Ctrl-X

Sounds like a question for the XP LogonUI & Boot Screenssubforum... Good chance the answer can be found over there as well.

That's not much use if you need to boot from a RBFG disk to connect to the RIS server in the first place

Try the installation with UnattendMode set to FullUnattended as suggested by cluberti.

I've seen this happen once when I applied an incorrect hotfix to my RIS image. This hotfix replaced the Ntldr file in the \\<server>\REMINST\Setup\<language>\Images\<image>\<architecture>\templates folder. After restoring the original Ntldr it was working again.

Not sure if I understand correctly, but the $OEM$ folder itself is deleted after setup is finished... That's why you should place files and folders you want to keep in one of the $OEM$ subfolders. Check the guide for details.

Are all disks connected to the same SATA controller?

Yup One question: what are the /GROUP switches you're using supposed to do? I can't find anything about this in the REG ADD syntax help.

Are you sure that Shortcut.exe is in the search path? Try specifying the complete path to the executable in your .CMD file.

Once again: Profile and Folder Redirection In Windows Server 2003. Everything you need to know about roaming profiles and folder redirection.

Excellent topic; should be made sticky IMHO

Sounds like this is a company managed computer, possibly through SMS. If that's the case, you probably won't be able to do anything about it.

Have you tried re-registering the DLL? regsvr32 regwizc.dll

Add the following to your answer file: [URL] AutoConfig=0

An easier way to edit Boot.ini is through MSConfig: How to Use and Edit Boot.ini in Windows XP

Might be related to this issue: Installation stops when you use a Windows 2000 RIS Server to deploy Windows XP Professional and Windows Server 2003 clients Some more reading you may find interesting: How to Deploy Windows XP Images from Windows 2000 RIS Servers

The suggested secedit method will only reset security settings to default: NTFS, registry en services permissions, user privileges - basically everything under the Security node in GPEdit. This won't affect any user interface restrictions, which are all registry-based settings, located under the Administrative Templates node. By the way: even if the restrictions were applied by editing the registry directly, they should still show up in GPEdit. After all it's the same registry entries, whether you change them in GPEdit or in RegEdit.

The redist is IExpress compressed. The actual installation program is DXSetup.exe, which can run unattended using the /silent switch. So this should do the trick: directx_aug2006_redist.exe /q:a /r:n /c:"dxsetup.exe /silent"

That's even stranger; a static IP address should always work, as long as it's in the correct subnet and physical network connectivity is OK... Are you absolutely sure you gave it a valid address and subnet mask? Have you tried replacing the network cable of the failing client? DHCP is a service running on one of the systems in the network... If you didn't install and configure it yourself, the router is probably acting as DHCP server. Usually it can be managed through a web interface.

ALLUSERS is a standard MSI property (not a switch), that can be set from the installation command line. Read all about MSI properties *here*.

That depends on what type of DHCP server you have... They might still have valid IP address leases, so you wouldn't notice if they had DHCP problems as well. Open a command prompt on one of the other clients and type "IPCONFIG /RENEW" to check if it can renew its IP address lease. If it can't, there's definitely something wrong with the DHCP server.

Check if any local policies are defined on the computer: Start / Run / "gpedit.msc" [Enter] to open the local computer's Group Policy settings. See if there are any local settings defined and remove them if necessary. [Edit]Changed instructions to open local GPO to a much easier method after reading allen2's post

This is a so-called APIPA (Automatic Private IP Addressing) address, which is configured automatically when no DHCP server is available. Check if the DHCP server is running and configured correctly, and check network connectivity between the client and the DHCP server.

The whole thing looks overly complicated to me... I don't understand the purpose of the IPTV.cmd. All it does is set an environment variable and then run the RunMe.bat, right? So why don't you run the RunMe.bat straight from Cmdlines.txt? In fact, why don't you run the "iptv viewer.msi" installation straight from Cmdlines.txt? Anyway, this MSI may just not install correctly at the T-12 stage... I'd move the installation to RunOnceEx if I were you. As long as the installation is performed under an Administrator account, the application will be available to all users. If needed, add "ALLUSERS=2" to the installation command line.

At what point did you insert the registry entries? If imported from Cmdlines.txt, I'd say it should work... You'll need the following entries: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AutoAdminLogon"="1" "DefaultDomainName"="DOMAIN" "DefaultPassword"="password" "DefaultUserName"="User"

Depends on the application. Search or post to the Application Installs forum.