dtakias

Same here, never managed to get that working properly via GPO. On the other hand, you can use Wireless Network Setup Wizard and make a USB stick with your new wireless settings Then plug that inside every laptop and double click the setupSNK.exe file inside it, or wait for the autorun process since the wizard creates an autorun.inf inside the USB. Copy the contents to a few USB sticks and you'll finish in no time...

Is the machine logging on to the domain? If yes is it roaming or mandatory profiles? In any case open registry, mount your network profile and navigate to HKEY_USERS\*your profile*\Printers\Connections see if anything is listed there...

Logon locally on the machine that has the ghost printers, open registry and navigate to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Connections See if the ghost printers are listed there and delete them. Reboot and see if that worked... If not look under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Connections" as well.

Not done it like this but what you could do is boot the system with UBCD , use the registry editor and navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current Version\WPAEvents Once you are there double click "OOBETimer" and change at least one digit of its value. That should force windows to deactivate itself, then if after you reboot you manage to get into windows run "%systemroot%\system32\oobe\msoobe.exe /a" and you should get the the activation screen that will allow you to enter a valid product key for the type of windows you are using. If it's OEM it won't take the VLK key though...

How do you assign/deploy the printers to your machines? Is the print server part of a domain? If yes does it run 2003 R2?

Open registry and navigate to: HKEY_USERS\.DEFAULT\Control Panel\Desktop Double click on "Wallpaper" string and enter the location of your background under Value data.

Yeah, you'll probably be able to make a universal image that will work on a few machines, but it's very difficult, almost impossible to make it work under every single chipset/board manufacturer. I still believe making seperate images is the way forward...maybe we windows 7 deploy tools will provide this functionality???

Same here, on the networks I support I place no files under NETLOGON.

Also do you point to the the packages via UNC path? Otherwise it will fail installing any of them.

Do the crashes start after she is accessing her files from the offline cache? How about the server copy of the files? If you access them directly can you open and save a document? Also have you tried "Detect and Repeir" under help menu ?

Something like a miniITX solution with the appropriate video outputs to connect to your tft ?

And built-in ethernet

Also you could use the EZ GPO Tool . It does power settings by user and computer... cheers

that might be the case, I've never had problems with syspreping SP3 machines but I always used the deploy package for SP3.

Since it only happens on your curriculum network is probably a profile issue? Are you using roaming or mandatory profiles? Maybe check the key in registry that does Power Configigurattion on your network profile: HKEY_USERS\"YourProfileName"\Control Panel\PowerCfg\PowerPolicies

There is probably a previously cached network connection on the system. There are 2 registry entries about network drives. Check them and see if there is any previously cached entries and delete them. Restart the machine and see if that got rid of the problem. The entries are under Current User: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 cheers

Try the Panasonic Toughbook 30 and maybe she'll change her mind

This tool is very usefull, I have it installed on my schools as part of monitoring who prints what and when.

Sounds like a job for this or this

I always reset/remove the imaged machines from the AD, as I've run into conflicts in the past when comes to GPO's associated with them. As said before a new computer object has to be created during sysprep. When comes to computer names inside sysprep.inf I enter the first part of the computer name, which consists of the OS and the room name/location and then a symbol. For example " XP203* " . When sysprep detects the symbol it will eventually stop and then I enter the remaining part which is the number of the computer.

That script worked really well, thank you. Also if you remove those files from the original MSI before you compress it and then deploy it, it doesnt complain and starts properly with no errors.

They probably use some sort of pre-activated keys for their OEM version of the OS. I'm pretty sure I've seen that many times with Toshiba laptops and desktops, as we work very closely with them.

I believe that you can tell whether your XP installation is VLK or OEM if you right click on My Computer and select Properties. Then go on General Tab, and under “Registered to:” you can see a product ID (divided into 4 seperated groups of characters). On an OEM installation, the 2nd group of characters is always OEM whereas on a VLK and maybe Retail as well, you will see numbers (such as 623). Also by looking at the file "setupp.ini" in the I386 directory of your XP CD, you can tell what kind of license key you have. An OEM version has the word “OEM” included in the line that says “Pid=XXXXXOEM” and a VLK versionI(possibly Retail as well) has just numbers.

When comes to Norton Ghost for enterprise the one you need to look into is Symantec Ghost Solution Suite That has got all the bells and whistles when comes to taking/editing/deploying images.

That's cool, will give it a go, thank you!