0 use?
A: In communicating with an upstream server or the Windows Update site, the
WSUS server will usually use TCP port 80 or 443. When client systems
communicate with the WSUS server, they either use TCP 80 or TCP 8530.
Q: In an environment where laptop users travel from offi ce to offi ce and site to site,
what topology would help in guaranteeing these systems get their updates from
the nearest WSUS server?
A: Using the roaming client topology will most likely be the best option.
Q: How do you force a WSUS client to look for new updates?
A: While logged on to the client run the wuauclt.exe /detectnow command.
Q: Does WSUS 3.0 support a Web-based administrative interface like previous
versions did?
A: No. It only supports an administrative console that uses MMC 3.0 or higher.
Q: What might be a good way to deploy and test updates on only a few client
systems?
A: Create and use Computer Groups from within the WSUS Administrative
Console.
Q: Where do you go to reconfi gure the synchronization schedule for a WSUS server
to either the Windows Update or an upstream WSUS server?
A: In the WSUS Administrative console on that server, go to the Console Tree, click
Options, then go to the Details Pane and select Synchronization Schedule.
Q: Why would administrators use Internet news groups to troubleshoot issues with
WSUS 3.0?
A: People in news groups can be your best asset in troubleshooting WSUS.
Pages:
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174