Thursday, May 24, 2012

Computers are Not Assigned, No Site Code

Hi, have you ever come across this problem before? I guess I’m not the only one out there with this problem.

I bumped into this problem again in a project recently. I’m using AD Site to set boundaries, and roughly 500 computers are unassigned. The first thing I do is export the IPs of those unassigned computers and ask customer to check with their AD Sites and Services. Ask them to include those which is not inside the AD Sites and Services.

Customer have included those subnets into AD Sites and Services, but the computers are still unassigned! Hence, I use IP Ranger to include those computers into the boundaries. This normally works for me, but not this time…

At last I’ve no choice but to delete those computers that are unassigned and then force the AD System Discovery. Guess what, the newly discovered computers are assigned nicely.

Thursday, May 3, 2012

GPO Startup Script is Not Working in Windows XP, but Working in Windows 7

My startup script is working fine in Windows 7 but not working in Windows XP. The script itself is confirm working fine, and this script have been used in many other projects previously. Thinking out of the box, I thought there are some settings or software blocking the vbs script, and hence I created a batch file to call the vbs script. Besides, I also added the server name to the Local Intranet trusted sites, but the luck is not with me. All I’ve tried were not working and these have drive me crazy for while until I found this post.

Solution: Enable the “Run startup scripts asynchronously” setting under Computer Configuration>Administrative Templates>System>Scripts in your GPO.

By default, the system wait for each startup script to complete before it runs the next startup script. After the setting enabled, the system does not coordinate the running of startup scripts. As a result, startup script can run simultaneously.