How to force windows updates with wuauclt.exe
In order to use WSUS the PC needs to be in Active Directory. Once the PC is in Active directory you can run:
wuauclt.exe /detectnow
This will force the PC to talk to WSUS to get the updates needed instead of waiting for the PC to talk to WSUS.
To view the log go to c:\windows\WindowsUpdate.log or Windows Update.log
In the log you can view any updates the PC may need if any at all.If you are having issues getting wsus updates try:
wuauclt.exe /resetauthorization /detectnow
This will force the PC to download a new certificate, and then download the updates from WSUS. Again check the log in c:\windows\WindowsUpdate.log to see if the Pc was able to reauthorize and obtain new updates.
Setting Mailbox Limits over 2GB
Setting mailbox limits over 2GB in Exchange 2003
Exchange Server 2000/2003 allows the Exchange Administrator to set limits on the mailboxes of users in the Exchange Organization (read Setting Mailbox Limits, Working with Store Policies and Overwriting Mailbox Store Policy Limits for more info). Setting limits on the mailboxes help control the database size and plan for efficient backup, restore and maintenance tasks.
However, in most scenarios, there will always be users that think that they deserve more storage space than they were given in the first place. Some of these are VIPs, others just need it for their work, and the rest are simply trying to make their life easier.
So, whatever may be the reason, you might find yourself in need to configure higher mailbox limits for some users.
Well, up to this point all I did was to explain what you already know. However, there is one tricky bit:
When trying to configure mailbox limits higher than 2097151 KB the Exchange System Manager (ESM) or Active Directory Users and Computers (ADUC) snap-ins will not allow you to enter these higher limits.
You will receive an error saying: “The value for ‘Issue warning at (KB)’ is not valid. Specify a value from 0 through 2097151″.
The mailbox limits are actually Active Directory attributes. If you set a sample user’s mailbox limits and look at the user object with a tool such as LDP or Adsiedit.msc you will notice that they are:
Issue Warning = MDBStorageQuota
Prohibit Send = MDBOverQuotaLimit
Prohibit Send and Receive = MDBOverHardQuotaLimit
These limits are part of the UI, and NOT a hard coded limit on the attribute itself.
Solution
AD Account Lockouts
如下，解决AD帐号 lockout的通用步骤是：
- 检查安全日志
- enable Netlogon 的log
- enable 帐号审计
- 最终解决问题的方法是更改DC服务器的IP地址。应该是有一个ldap的服务出了问题
- 问题应该是从一个信任域传过来的
Account Lockouts..
2小时修复vista启动问题（crcdisk.sys）
一次非正常断电后我的
Vista不能正常启动了。进入安全模式后发现系统启动到crcdisk.sys时就停止了。使用Vista安装盘启动后，选择了自动修复，运行半个多小时后Vista告诉我不能自动修复此问题。浪费我的时间。
幸好有个网站叫Google.我也还有一台电脑可以上网。Search之后，下面这个方法解决了我的问题。
- Vista安装盘启动
- 使用command窗口
- 进入c:\windows\system32\drivers
- 将pcmcia.sys改名为pcmcia.old
- 重新启动
这次成功的启动了Vista。重新安装pcmcia驱动后一起回复正常。
A Solution to “Another blog is already hosted at this address.” error
A solution has been found…..
The problem stems from Google Apps for Your Domain….here is how I
fixed the issue of the “Another blog is
already hosted at this address.” error.
1. Go to your domain registrar, (I needed reset everything to their
default settings) and create (or change if already existing) a CNAME
named “www” and point it to “ghs.google.com”
2. Logged into Google Apps for Your Domain or create a new account if
you do not have one. (I had decided to set up an account AFTER
originally setting up my custom domain on blogger.com….this
inadvertently led to all of my problems)
3. Once logged in, from the “Dashboard” choose to ONLY add “Domain web
pages” and click the “Add selected services” button.
4. Use the CNAME subdomain that has been giving the message “Another
blog is already hosted at this address.” error in Blogger as the
address you want to publish to. (In my case “www”)
5. From here I chose to create a simple “Google Pages” webpage just to
confirm that my address (http://www.websitefreetips.com) was indeed
working.
6. Back on the Dashboard of Google Apps for Your Domain, choose to
remove the “Domain web pages service”
7. Go to your blog on blogger.com and change the custom address to the
problematic address (In my case “www.websitefreetips.com“), blogger should
now allow it.
8. In my case, when I would click the “View Blog” link…blogger now
took me to the Google Pages page I had just created in Google Apps for
Your Domain.
9. This step my be redundant and actually just require time for the
DNS to refresh, but I logged back into Google Apps for Your Domain and
proceeded to add the “Domain web pages service” back, but this time I
used a different subdomain (not “www” but instead I used “blog”). I
never bothered to set up a CNAME in my registrar settings as I was
only attempting to get Google Apps for Your Domain to “let go” of the
“www” subdomain.
10. All of these actions soon caused the “Google 404 not found” page
to appear for my site address.
11. I then proceeded to again remove the “Domain web pages service”.
12. After only a few moments of waiting for the DNS to catch up, my
domain (http://www.websitefreetips.com) was now working and opening my
blog.