Ctrl-X

Office Shrinker?

Should be posted in the nLite forum.

You can only use that option when you're installing Windows via winnt32.exe: You're probably better off specifying UnattendMode=DefaultHide in your answer file and then leaving out the ComputerName, FullName and OrgName entries. That way you'll be prompted for this information during setup. It sounds like the installation is rolled back. By default Office 2003 creates installation log files in the %TEMP% folder. See if there's any error messages in those. You may need to specify the full path to the transform file, but I'm not sure about that. Alternatively, use the /qr switch instead of /qb- to get some more information during Office setup.

http://www.msfn.org/board/index.php?showtopic=84893

oioldman did, too! Great minds think alike Check the log file (should be in the Windows folder) for errors. If there's any "Access denied" messages, see *this topic*.

Why don't you follow the directions the error message is giving you? Boot from the Setup CD and press "R" at the first screen to repair Windows.

Firewall settings can be managed through Group Policy. Here's how: Managing Windows XP Service Pack 2 Features Using Group Policy

Same here The only lines you need to add to dosnet.inf are [OptionalSrcDirs] svcpack Why did you make the other changes? This line should read: Signature="$Windows NT$" So there's two dollar signs in the signature string, one at the beginning and one at the end. In fact I think I posted this before...

You can uninstall any installed language pack via %windir%\mui\muisetup.exe.

Welcome! FYI: there's an Introduce yourself subforum

You're not the only one: http://www.neowin.net/forum/index.php?showtopic=427285 http://forums.wugnet.com/windows/modules.p...pdate-installed Google is your friend!

If this is an Active Directory domain, you can easily deploy a Group Policy Object to add this domain user to the local Administrators group on all workstations.

http://msdn.microsoft.com/embedded/

Press Ctrl-Alt-Delete twice at the Welcome screen to switch to the classic logon screen, log on using the Administrator account and then delete the other one.

That's right. Well, that depends on your point of view... The page you downloaded the language packs from clearly states they are for Windows Embedded, so you can't blame MS for the fact that you didn't understand that immediately. The "regular" Windows XP Multilanguage User Interface (MUI) packs are available to Volume Licensing program customers only. I suppose this is one of the benefits of having a Volume Licensing agreement.

Of course It's not on the disk; it's a label that's attached to the system case somewhere... Check the page I linked to in my previous post for some examples of what it might look like.

Should be posted in the nLite subforum.

http://unattended.msfn.org/unattended.xp/view/web/27/

These language packs are for Windows XP Embedded and intended for use by Windows Embedded developers.

A Certificate Of Authenticity See *this page* for more info. If it's in the Add/Remove Programs list and it has a Remove button, you should be able to uninstall it.

Don't use a CMD file; a smart user will be able to find it in the SYSVOL share and read the password. Run NET.EXE with the appropriate parameters straight from the GPO startup script instead. Probably not completely secure either, but at least it's harder to find.

AFAIK, WMP 9 was included with XP SP2... Doesn't she have that installed? If not, maybe uninstalling WMP 10 and then installing SP2 will solve her problem.

Just for the record: another option would be to set the "Flags" DWORD value in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx to "0x00000080". This would disable the status dialog completely. Other values are possible, for instance to create an execution and/or error log file. See Syntax for the RunOnceEx Registry Key for details.

Add/slipstream SATA drivers - A fully working solution

Here I am I'm sorry, but I can't imagine what's going wrong... Are you really really sure the user in question is getting the correct combination of policy settings? To make sure, run the Resultant Set of Policy snap-in (rsop.msc) under that user's account. If the settings appear correct, post the results here. There may still be something that's overlooked...