中文资源，详细列出各种WSUS资源：
http://gnaw0725.blogbus.com/logs/19880145.html
Showing posts with label WSUS. Show all posts
Showing posts with label WSUS. Show all posts
2008-09-24
2008-09-22
WSUS troubleshooting,
http://www.wsus.info/forums/index.php?showtopic=9312
Client-related
Do my clients meet the requirements to run WSUS?
Have you cloned your computers on the network? If yes, did you run Sysprep, Ghostwalker, or NewSID on the computers after they have been deployed with the new image?
Active Directory
Did you apply your GPO to the appropriate OU? Did you apply the GPO to an OU that contains computer objects?
Are you waiting long enough for your GPOs to be applied to your computers?
Is the GPO even applying to your computer?
Do you have 'Block Inheritance' set on your OU which would restrict a group policy from applying to the OU and objects contained therein?
Tools for troubleshooting:
client diagnostic tool
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
server diagnostic tool
http://download.microsoft.com/download/7/7/4/7745a34e-f563-443b-b4f8-3a289e995255/WSUS%20Server%20Debug%20Tool.EXE
Want to figure out which computers have duplicate SIDS?
Use psGetSID from Sysinternals: http://www.microsoft.com/technet/sysinternals/utilities/psgetsid.mspx
- You can run this against all computers in your domain to discover who has a duplicate SID.
You should really then run NewSID from Sysinterals on any of the duplicate computers to resolve any potential issues in the future (not to mention the security issues involved with having duplicate SIDS on the network): http://www.microsoft.com/technet/sysinternals/utilities/newsid.mspx
NOTE: You don't need to RUN NewSID on each computer prior to fixing the duplicate ID issue in WSUS, but it may rear its ugly head later on, so if you can find the time, I would recommend fixing this issue as soon as you can.
Error: this computer has not reported yet, wsus
Error: this computer has not reported yet, wsus
Qeustion:
Just set WSUS up in a test enviroment and im getting an error regarding my
client machine "Not Reported Status Yet" in the computers section. The
computer is added to a test group and this is a Fresh Windows XP SP" client,
2003 Server SP1.
My server is fine it's just the client where im having the problem.
Answer 1:
"Not Yet Reported" is a normal indication between the time a client first
registered (and probably is selfupdating), and completes a detection cycle,
including a reporting event. This delay is normally about 20-30 minutes,
though, so if it has been more than an hour since the client "Last
Contacted" the WSUS server, you may have a malfunction on the client side.
Start by running the Client Diagnostic Tool and posting the results. If the
output of the CDT looks normal (post the results anyway), then continue by
inspecting the %windir%\WindowsUpdate.log for error diagnostics.
Answer 2:
I don't know if it'll relate to your specific situation but I had an issue
last week where two pc's were imaged with the same Windows seat id from
Dell... WSUS will only recognize the most current machine put on the
network.
What actually happens it that WSUS recognizese the most recent machine that
/reports/ to the WSUS server if those machines have been built from
improperly prepared images.
If you're able to monitor the server closely, and frequently enough, you'll
actually see the machine name bounce between the two identical clients, as
each one executes a detection/reporting event.
Qeustion:
Just set WSUS up in a test enviroment and im getting an error regarding my
client machine "Not Reported Status Yet" in the computers section. The
computer is added to a test group and this is a Fresh Windows XP SP" client,
2003 Server SP1.
My server is fine it's just the client where im having the problem.
Answer 1:
"Not Yet Reported" is a normal indication between the time a client first
registered (and probably is selfupdating), and completes a detection cycle,
including a reporting event. This delay is normally about 20-30 minutes,
though, so if it has been more than an hour since the client "Last
Contacted" the WSUS server, you may have a malfunction on the client side.
Start by running the Client Diagnostic Tool and posting the results. If the
output of the CDT looks normal (post the results anyway), then continue by
inspecting the %windir%\WindowsUpdate.log for error diagnostics.
Answer 2:
I don't know if it'll relate to your specific situation but I had an issue
last week where two pc's were imaged with the same Windows seat id from
Dell... WSUS will only recognize the most current machine put on the
network.
What actually happens it that WSUS recognizese the most recent machine that
/reports/ to the WSUS server if those machines have been built from
improperly prepared images.
If you're able to monitor the server closely, and frequently enough, you'll
actually see the machine name bounce between the two identical clients, as
each one executes a detection/reporting event.
Subscribe to:
Posts (Atom)
Posts
