Greg your the Man! Thanks for the reg key info and the "wuaclt
/detectnow" info. I remember there was a command line way to force it to
check but too lazy to look for it. So you answered my laziness for me.
I think a combination of nLite customized xp install to include
something's in the install
Some other useful notes:
"net stop wuauserv" stops the Automatic Updates (AU) service so it will pick
up the new config. Change to start, obviously, to restart it.
"wuauclt /detectnow" forces AU to detect if updates are needed immediately.
c:\windows\WindowsUpdate.log provides a verbose log file
At 03:04 PM 20/02/2008, Greg Sevart wrote:
Oh, absolutely. You also don't need a domain and group policy--you just use
a .reg file to add the WSUS server info, then delete the key when you're
fully patched. We use it internally to bring new machines up to date
-before- joining the corporate domai
Oh, absolutely. You also don't need a domain and group policy--you just use
a .reg file to add the WSUS server info, then delete the key when you're
fully patched. We use it internally to bring new machines up to date
-before- joining the corporate domain.
Here's a sample wsus-enable.reg file:
W
nLite has it's place when making custom install XP
CD's.
Autopatcher was quite good and is not dead but rather
they've been forced to
change tack by scripting the downloads (to come direct
from M$ servers) needed
to create the packages. Right now it looks like the
downloader has some issues
wit
At 01:58 PM 20/02/2008, Mesdaq, Ali wrote:
I would be very hesitant to trust some free tool. But if you could
install with a xp sp2 install then connect to your own internal WSUS
server for updates post install patching could go from 2hrs to 20min.
Can I use an WSUS server in a repair shop? Ev
I would 2nd not using 3rd party tools for this kind of stuff unless its
a up to business par. I worked for a company who was the pioneer of
windows patch management and trust me its a VERY hard thing to do right
I would be very hesitant to trust some free tool. But if you could
install with a xp sp
At 07:06 2/20/2008, Brian Weeden, wrote:
>Having going through the a&&pain of multiple reboots and patching for
>a new windows install too many times myself, I wanted to pass along
>this little gem that I don't think has been mentioned here before:
>
>http://www.heise-online.co.uk/security/Do-it-yo
Oh absolutely, the chipset does play a huge role, but I fear we're
going to start running into the limits of the signal traces over the
board itself AND timing issues derived from having two drops on the bus.
On 20 Feb 2008, at 13:33, Greg Sevart wrote:
Oh, the chipset plays a huge role. Th
Yes, AFAIK you need to log the machine into a domain, have it accept a
group policy that sets the update repo path, do the updates, and then
disjoin it from the domain and pray that the GP doesn't stick around
after that.
Thane Sherrington wrote:
At 09:48 AM 20/02/2008, Greg Sevart wrote:
T
Looks nice, just rebuilt 2 PC's this weekend and even using XP with SP2,
there were 102 or so updates needed and it takes forever.
>>Having going through the a&&pain of multiple reboots and patching for
>>a new windows install too many times myself, I wanted to pass along
>>this little gem that
At 09:48 AM 20/02/2008, Greg Sevart wrote:
Thane,
I'm actually kinda surprised you don't just run an internal WSUS server for
in-house patching. I've always preferred it over third party tools. Sure, it
still requires multiple reboots, but at least pulling updates is nearly
instantaneous. After
Thane,
I'm actually kinda surprised you don't just run an internal WSUS server for
in-house patching. I've always preferred it over third party tools. Sure, it
still requires multiple reboots, but at least pulling updates is nearly
instantaneous. After a couple botched systems caused by Autopatche
Hi Brian,
Thanks for the tip, I'm definitely going to try this out.
T
At 09:06 AM 20/02/2008, Brian Weeden wrote:
Having going through the a&&pain of multiple reboots and patching for
a new windows install too many times myself, I wanted to pass along
this little gem that I don't think
Oh, the chipset plays a huge role. The communication you speak of is
(largely) regulated the NB in question. An exaggerated (because it has other
problems) example is the 680i chipset. Even P965's are generally capable of
running higher FSBs with QC chips than it can. Alternately, you can look at
t
Having going through the a&&pain of multiple reboots and patching for
a new windows install too many times myself, I wanted to pass along
this little gem that I don't think has been mentioned here before:
http://www.heise-online.co.uk/security/Do-it-yourself-Service-Pack--/features/80682
It's an
The issue with the twin-die arrangement on the current intel quadcores
is that it's not the northbridge that generates the FSB wall, it's the
blend of both cores and the need for everything to communicate
properly, I've had an E8400 on a 500Mhz FSB (P35 chipset) for a few
weeks now and it's
17 matches
Mail list logo
