ravashaak

If I told you one way or the other, I'd just be guessing. So, I really can't answer your question without attempting your method myself. However, you may have another alternative. If your laptop's NIC and BIOS support booting from the network, you could potentially perform a network boot and then install XP from a network install point. There would be some work involved in getting everything working, of course. However, it might be a viable alternative. Good luck! - Ravashaak

Well, at first glance, I can see at least one problem with your AdAware install. Your code for installing AdAware references an "AdAware" folder: start /wait %systemdrive%\install\Applications\AdAware\aaw6181.exe /s However, your screenshot of your directory structure indicates that the directory is actually called "adware" not "adaware". So, that would definitely cause a problem. As far as PowerToys is concerned, it appears that you merely forgot to include the "applications" directory in the path statement for your install code: start /wait %systemdrive%\install\PowerToys\TweakUI.msi /qb The above path does not include the applications directory. Since the applications directory is part of the path, your installation fails. Some advice: Anytime one of your installs fails and complains about not locating a file, etc, triple-check your path AS WELL AS your filenames! Hope this helps. - Ravashaak

It's a Windows 2000 Resource Kit utility. - Ravashaak

Here's what I do to change the name of my admin account during the unattended install: %systemdrive%\install\CUsrMgr -u "administrator" -m \\%computername% -r "bigkahuna" %systemdrive%\install\CUsrMgr -u "bigkahuna" -m \\%computername% -S passwordneverexpires %systemdrive%\install\CUsrMgr -u "bigkahuna" -m \\%computername% +S mustchangepassword I utilize cusrmgr.exe to accomplish this and other account-related tasks. It really is a good tool once you establish the needed syntax. The first line of code accomplishes your goal, changing the default administrator account name to "bigkahuna". The next two lines of code I just throw in for free. Maybe you will find them useful, or maybe not. Respectively, they unset the "password never expires" property for the account, and require a password change at next logon (since I don't like to include my real admin password in the winnt.sif file). With this setup, when I perform my first manual logon, the account has already been renamed, and during authentication will prompt me to change my password - a nice reminder!). BTW, you must first unset the "password never expires" property before setting the "must change password" property. - Ravashaak

Here's a couple of links on the subject: Link 1 Link 2 Hope this helps... - Ravashaak

If you are performing your unattended install on a domain computer, do you have a default domain profile defined for users? If so, perhaps the profile is conflicting with and overriding some of your current user tweaks. If you suspect this may be the case, create a LOCAL user on your newly-installed system. If the local user has the tweaks, but the domain users do not, then the defualt domain profile is most likely the cause.

I'm attempting to install the Go-Global UX Windows client. Sorry for not making that clear.

Does anyone know how to install Graphon Go-Global in an unattended fashion? This is one of the few apps that's managed to stymie me to this day. Any help is appreciated.

I'd recommend scanning the system with HFNetChk. Make sure to use the -v (verbose) option. My guess is that a registry value did not get written. Sometimes HFNetChk can inform you of the specific problem.