edwalt's - Things I Wish I'd known about SBS 2003....
This error can be triggered by several different issues:
1. The Client Firewall is enabled.
Ports needed: TCP Ports: 8530, 8531, 5723, 51906, 135, 445, 139 UDP Ports: 137, 138. These ports are necessary for client installation and basic communication between SCE clients and the SCE server.
Ports needed:
TCP Ports: 8530, 8531, 5723, 51906, 135, 445, 139
UDP Ports: 137, 138.
These ports are necessary for client installation and basic communication between SCE clients and the SCE server.
2. Automatic Updates Service is disabled on the clients.
3. WSUS URL's are set incorrectly in the registry on the clients.
The WindowsUpdate.log is usually very helpful with WSUS connection issues. Not to be confused with the Windows Update.log <Note the space between the words>.
To verify the current client WSUS registry settings:
HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate - verify that the following settings are there:WUServer – https://<SCEServer>:8531WUStatusServer - https://<SCEServer>:8531AcceptTrustedPublisherCerts – “1”
If the registry keys are incorrect - modify the key
You can force the client to contact the WSUS server by running "wuauclt -detectnow" on the client
4. The SCE Group Policies are not linked to the Default Domain Policy
Note: By default Group Policy takes 90 minutes to push down the configuration to the server and client machines.
If you would like a computer to pull down the new group policy configuration you can go to the server machine Open a command window by going to Start > Run > and type cmd. Once the command window is open you need to type in gpupdate /force.
To verify if the Group Policy configuration has been applied to the server - Start > Run > and type rsop.msc and scroll to Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall\Domain Profile\ and see if the IP address exceptions set for remote administration exception and file and printer sharing exceptions were applied to the local machine.
5. The clients are not members of the SCE_Managed_Computers security group.
By default, computers in the "Computers" container are added to this group automatically. If computers are located in other containers they will need to be added to the group manually.
6. File and Print sharing is not enabled on the client
>edwalt
cMjjdw r u crazzy? I told u! I can't read!
E7JBen r u crazzy? I told u! I can't read!
bNWNSD r u crazzy? I told u! I can't read, man!
2m0ih6 r u crazzy? I told u! I can't read!
vhfZ1a r u crazzy? I told u! I can't read!
kgf8MU r u crazzy? I told u! I can't read!
XI2qtc r u crazzy? I told u! I can't read!
KIO8Ou r u crazzy? I told u! I can't read!
3YzuG2 r u crazzy? I told u! I can't read!
qnIOMS r u crazzy? I told u! I can't read!
PingBack from http://www.killthoseads.com/?p=2331
On step #4, can the gpo changes me made on the OU that have the SCE computers? I have the a SCE GPO applied at the SCE_Computers_Group_ OU and have inheritance blocked. Will this work?