merowinger

yes the user is prompted for administrator password

I have the following unattend.xml, to create a partition D:\ which size is the remaining disk space of the hard disk. Drive C:\ shell be 15 GB and D:\ the remaining... But it does not work, nothing happens! Drive C:\ is already installed and should not be formatted <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>15000</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Type>Extended</Type> <Extend>true</Extend> <Order>2</Order> </CreatePartition> <CreatePartition wcm:action="add"> <Type>Logical</Type> <Order>3</Order> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Letter>C</Letter> <Label>OS</Label> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Label>Data</Label> <Letter>D</Letter> <Order>2</Order> <Format>NTFS</Format> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> </DiskConfiguration>

its business no i dont use vLite! I just did some testing! Clean manually DVD Installation: - User created during setup - is getting uac messages - User created afterwards with membership in group "administrators" - is getting uac messages - User created afterwards with membership in group "users" - is NOT getting uac messages - After all this test...enabled BuiltIn Administrator account - is NOT getting uac messages One more clean DVD installation and sysprepped with my administrator enable command line -The same result as listed above So that all seems default..no bug! Do you have the same results? Summary: -The BuiltIn Admin Account is never getting the UAC message -Users with local Administrator rights get the message -Users without local Administrator right does not get the message, because they have no rights to dstroy something....open regedit.exe is working but not changing something

i just noticed that only members of the local "users" group can start regedit.exe .... without getting the uac popup message! All members of the local "administrators" group get the message...what is correctly

i have a strange problem...it seems that when i enable the local administrator account in windows vista during the unattended setup (specialize phase -> RunSynchrounus Command) with this command line: net user Administrator /active:yes ...that no UAC popup window appears when i start e.g. regedit.exe or lusrmgr.msc. The UAC is listed as "running" in control panel. So what's the problem? I want UAC to be enabled and the popups the be shown...

hi all, i just create a vista unattended installation, where i have one question... This a the planned procedures step by step: 1. Inject drivers in install.wim 2. Install a Master Computer manually with the custom install.wim 3. Make some further customizations 4. Run a sysprep with unattend.xml option 5. Capture a image of the harddisk, or clone it... My problem is step 4... On first start of the sysprepped computer the only option where should be configured manually, is the computername! I just take this sysprep options: sysprep.exe /generalize /shutdown /oobe /unattend:.\unattend.xml Is the /oobe option correct, or do i need the /audit option! Also do i have to enable the "SkipUserOOBE" and "SkipMachineOOBE" option in my unattend.xml? Any help would be cool! Thank you

if the hotfixes are .msp based then yes! All icons in the updates folder are installed in the windows search order.... i just cannot say 100% if the order is rightly used! Give it a try

you can delete it, but it will be recreated with the next change on the office 2007

the problem is, when you create a .msp e.g. only for publisher and infopath and execute it on a computer which already has installed excel, word, then those components will be uninstalled! So i think there's no other way to reinstall the complete office suite with the new msp! Or a manually way...to start setup.exe (or add/remove program repair) on those computers and add it manually!

msiexec /i <path>\proof.msi LAUNCHEDBYSETUPEXE=1 /qb The LAUNCHEDBYSETUPEXE parameter is the reason why you got this error.... Note: The above listed command is a unsupported way!!!!

As i read, there are several restriction editing the config.xml when deploying with Group Policies! The only options which can be configured are Product ID number, the language, the installation state and the installation source location Also make sure the config.xml is in the same folder as the msi file

you can't reduce the installation size (only with disabling some features)...but the MSOCache on your Systemroot stores always all components of office. But what you can do, is to reduce the size and duration during the installation with the following parameter in the config.xml LIS CACHEACTION="CacheOnly" You have to trigger the installation again, because this parameter forces to store everything first local in the msocache

no there's no msi available! You have 2 possibilities... 1. Deploy the .exe with script or somthing else to the clients 2. Extract the .exe into the .msp files and update you installation point by copying into the updates folder

there's a possibily...check out this! http://pleasepressanykey.blogspot.com/2008...-of-single.html

what about configuring the workgroup template path with group policy?