duomenox

Here is the webstie for creating users during the unattended install process: http://unattended.msfn.org/intermediate/users.htm The way I do it is that I have my cmdlines.txt file as follows: [Commands] ".\useraccounts.cmd" "REGEDIT /S regtweaks.reg" ".\RunOnce1.cmd" Then my useraccounts.cmd is where I add my users and reference the autologon registry entry... I add the user Local Account, add the Local Account user to the administrator group, disable the Administrator account, remove the password age requirement, and lastly call up my autologon.reg. UserAccounts.cmd net user "Local Account" "PASSWORD" /add /y net localgroup Administrators "Local Account" /add net user "Administrator" /Active:no net accounts /maxpwage:unlimited REGEDIT /S autologon.reg EXIT AutoLogon.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="Local Account" "DefaultPassword"="PASSWORD" "AutoAdminLogon"="1" This requires that the Winnt.sif has the following options defined: Winnt.sif (partial) [Unattended] OemPreinstall = Yes OemFilesPath = .\$OEM$ It works flawlessly for me... Some key points: Remember the name is CMDLINES.TXT CMDLINES.TXT should be located in the D:\$OEM$ folder (Subtitute you CDROM Drive Letter for D:\) The CMDLINES.TXT has very limited comand line functions, keep it basic. Place all files that CDMLINES.TXT will execute in the same folder as CMDLINES.TXT And that is it, hope you can get your CD working!

First of all I apologize for not doing much research, my dealine for this project has been bumped WAY up. I was curious to know if anyone has modified the bootfix.bin (the file that prompts you to "Press any key to boot from CD...") so that it will check for a file on the hard drive before prompting? Basically, I want to have a CD automatically boot unless it can find a file on the hard drive. I need to make a 100% unattended install cd for windows xp (which I have completed) but the CD requires a reboot after ghosting the HD. I do not want users to have to press any key to boot from the CD, but I don't want it to keep looping at the ghost phase. (I have to use ghost because of some smecific utility partitions and I don't want to use WinPE or BartPE) Ideally, the CD would boot, ghost the empty HD Image with a fully set up partition table and clean formatted partitions (and a file called restored.dat) The PC automatically reboots, then when the CD starts to boot again, it finds the Restored.dat file on the HD and allows the computer to boot from the HD instead of the CD... where the XP install is already waiting to continue. Any Ideas? Thanks for the help.

There are only a handful of companies that manufacture blank media. All the labels like Memorex, Sony, Yamaha, etc, buy them and slap their label on them. if you goto www.cdrmediaworld.com or www.cdmediaworld.com (if it is still up) they have a tool to extract the true manufacturer of the media so you can be better informed. The problem is more than likely the DVD-ROM in the server than the DVD+-RW. How old is the server, many DVD-ROM drives were not multi-format until the last year or so, and many, many thin DVD-ROMs (like the ones in laptops) are not truely multi-format. Does the server read the media ok on the first burn, but not after an erase and re-burn? If so, the problem is probebly the server's drive. Depending on the burning software and hardware you are using, there may be options to increase compatibility of burned discs, that be of some help. Also, try doing a full erase instead of a quick erase on the media before re-burning it. That can also help cure these types of issues.

How did you get your key? Did you buy a retail version of XP, did you get one when buying your computer? or did you get one from a volume license agreement (corprate version)? If you have a sitcker, then you most likely have an OEM Key that will require an OEM CD. All the infor for key verification is stored in setupp.ini under the 1386 directory on the CD. Search google for setupp.ini and you should find the right combinations to use for the key type you have.

Got it! Everything is working, the transform files are also working, but only if you add them to the command line (not from the setup.ini) Setup.exe PIDKEY=(25-digit key) TRANSFORMS=MSTFile.MST /qb- That was the final command line I used. Again, thanks for all your help, this saved me lots of reserach time!

I just tried it in my "lab" is it is clearing out the product key. So thanks for your ideas, it REALLY helped!

Yeah, I am restricted to the OEM CD that is sent with Dell PC's (and it is office basic edition) so the registry hack will most likely bemy best solution. I tried using the following lines setup.exe /jm basic11n.msi /t mstfile.mst but I was getting an error about the edition not supporting MST files. Which was strange becuase I could install using the MST and inserting the key previously The only question I would have is concerning the first run after I delete the key... do you know how I might be able to clear the key from the install screen? Is it stored in the registry again (possibly) or maybe in a config file in the office directory? Just curious to konw if anyone figured that one out again. Not to big of a deal because I can use a Key that will not activate. but I need to protect this CD from ambitous employees taking it home... Thanks again for your help, it has saved me tons of time!

Hi eveyrone, Question about unattended Office 2003 install. I have an MST which works great when I plug in the Product Key... but... I need to install Office 2003 without a product key, so that when the use first launches any office program, it then asks for the product key. I cannot seem to find an answer anywhere on the forum, or using google, or searching microsoft.com. The answer is not in the Unattended CD/DVD guide from msfn (which is awesome, just lacking this particular answer). Any ideas?

First of all I apologize for not doing much research, my dealine for this project has been bumped WAY up. I was curious to know if anyone has modified the bootfix.bin (the file that prompts you to "Press any key to boot from CD...") so that it will check for a file on the hard drive before prompting? Basically, I want to have a CD automatically boot unless it can find a file on the hard drive. I need to make a 100% unattended install cd for windows xp (which I have completed) but the CD requires a reboot after ghosting the HD. I do not want users to have to press any key to boot from the CD, but I don't want it to keep looping at the ghost phase. (I have to use ghost because of some smecific utility partitions and I don't want to use WinPE or BartPE) Ideally, the CD would boot, ghost the empty HD Image with a fully set up partition table and clean formatted partitions (and a file called restored.dat) The PC automatically reboots, then when the CD starts to boot again, it finds the Restored.dat file on the HD and allows the computer to boot from the HD instead of the CD... where the XP install is already waiting to continue. Any Ideas? Thanks for the help.

Thanks for the replies! I did a bit of reading on HTA and finally realized that HTA is HTML with a few extra HTA options availiable. I appreciate the info, I am working on converting the scripts. I will also try to use the files that came with AutoIt to get the scripts running in WinPE, I will let you know the exact procedure if I get it working... Thanks for the advice mbouchard! I don't know why I didn't think about injecting those files onto my CD....

Thanks for the suggestion, I've never worked with HTA files before, but they don't seem to complicated. I'll do some searching for some HTA references... Do you happen to know of any editors that include HTA text color coding? I've been using Crimson Editor for most of my programming... but I don't think it supports HTA syntax (for the color code). Thanks for the help.

Just to clarify, Can you sucessfully complete the txtmode portion of setup? Can you create and format a partition in txtmode? If you answered yes to both, it sounds like an issue with the driver itself. Have you made sure you have the newest driver? If using greenmachine's method... make sure you copied out the correct lines form the inf. I have used his method to include many RAID drivers and have not had an issue yet... but I have not tried with the HPT. Also, make sure that if you are using an unattend file that the MassStorageDrivers section has nothing in it (if you use GreenMachine's method). That will wreck havoc on the GUI Setup Portion. Post back with any more info.

Yeah, they give us a bit of extra job security The scripts he gave me are basically scripts that prompt the user for data specific to their situation (we have some clients that need a restore CD for their office computers located at their resturants [excuse the spelling]) And they have a specific guideline for computer name, company name and user name that is used during setup. The script I am referring to asks for their store number, and dell service tag and generates an answerfile that can be used with an unattended install of Windows. Currently he has been using them to run sysprep at the end of the unattended install (using generic info) when windows is completely loaded, to gather the info and automate sysprep... but this is a longer process... I am just experimenting with ideas untill my legal dept clears the use of WinPE this way.

The setupp.ini file in the i386 directory is the only file that dictates what key can be used during install. If you are using an oem key, you need to get the setupp.ini file from the OEM CD that came with your PC (like Aegis said). SP2 will modify this file, so if a straight copy will not work then you will need to slipstream SP2 onto the OEM CD. Just copy the OEM CD to a directory on your hard drive, then slipstream SP2 into it and make a new bootable image. That will take care of it unless your OEM Key was blacklisted. If you got your Key from Dell... you will have to call them for an updated SP2 CD as they have a specific set of Keys from MS and use an alternate method for validating the install. If you have any questiosn or need to download an image building utility see the unattended CD/DVD creation guide (linked at the top of the page).

Hey everyone, I was just given a large amount of Auto-It scripts that my boss wants converted into WSH so it will run in WinPE. (I don't know why, and right now is not a good time to ask him). Has anyone been able to get compiled Auto-It scripts to run in WinPE? If so, that would make my next few weeks so much better If so, how did you do it? Again, this is mostly wishful thinking. I think I have not tried it with BartPE, however the company I work for doesn't like to use BartPE, our legal dept has issues with the license agreement (they are paid to be a bit paranoid). Thanks for any replies!

If you want to format FAT32 and optimize it for conversion to NTFS copy oformat.com and cvtarea.exe from the WinXP Deployment Kit (or the Server 2003 Deployment kit) to your WinPE disc. (The deployment kit can be found on the XP or 2003 CD as deploy.cab under CDROOT\Support\Tools) Add the following lines to your boot process, oformat c: /a:8 /v:"(Volume Name)" /q cvtarea c:\cvtarea.tmp 1024 MB /contig /firstcluster 3 gb That was assuming you have a drive that is 10GB or larger. To convert from FAT32 to NTFS use the following command convert c: /fs:ntfs /cvtarea:cvtarea.tmp If you format your drives using this procedure and use cvtarea.exe to create a place holder for the NTFS MFT files your coverted NTFS partition will be almost as effiecient as a native NTFS format. We use this procedure because Ghost Corp 8.0 cannot write to an NTFS partition in a ghost image.... so we keep all our images FAT32 and convert to NTFS during the configuration process. One last thing, If you convert your system drive to NTFS while in windows and want to script the converstion process you will need to use the following line cmd.exe /C "echo y | convert c: /x /fs:ntfs /cvtarea:cvtarea.tmp" This will bypass the request to force a dismount, then supply a yes answer to the "would you like to convert during the next reboot" question... the cmd /c will close the command window opened to run the command directly after the command finishes. Use this method if you have a practical need to have your partiitons FAT32 (like for read/write use in ghost).

Ok, well I have come to the conclusion that I need to go to bed earlier :-P I misspelled the GUIUnattended Section as GUIUnattend (forgot the ed) Well I guess this post will be useful to someone who needs to debug their network settings in they sysprep.inf (that config was a complete b****) Anyways, sorry bout that

Hello everyone, I have made several SysPrep.inf files and this is bogglnig me... It keeps asking for user input when I have all the settings in the file for a fully unattended "install". Here is my file, can you see anything that might be an issue. I had this issue before adding all the networking sections, and those work perfectly (after many, many different trys) [Unattended] InstallFilesPath=C:\WINDOWS\i386 KeepPageFile=0 OemSkipEula=Yes ResetSourcePath=C:\WINDOWS [GuiUnattend] AdminPassword=(Encrypted Password) EncryptedAdminPassword=Yes OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=4 [UserData] ComputerName=(Comp Name) FullName=(Full Name) OrgName=(Org Name) ProductKey=(Product Key) [Display] BitsPerPel=32 Xresolution=800 YResolution=600 [Identification] DomainAdmin=(Domain Admin) DomainAdminPassword=(Domain Pass) JoinDomain=(Domain Name) [Networking] InstallDefaultComponents=No [NetAdapters] Adapter1=params.Adapter1 Adapter2=params.Adapter2 [params.Adapter1] INFID=pci\ven_14e4&dev_1677 ConnectionName=(Connection 1) [params.Adapter2] INFID=PCI\VEN_8086&DEV_1229 ConnectionName=(Connection 2) [NetClients] MS_MSClient=params.MS_MSClient [NetServices] MS_Server=params.MS_Server [NetProtocols] MS_TCPIP=params.MS_TCPIP [params.MS_TCPIP] AdapterSections=params.MS_TCPIP.Adapter1,params.MS_TCPIP.Adapter2 DNS=Yes DNSSuffixSearchOrder=(Domain Name) UseDomainNameDevolution=Yes EnableLMHosts=No SyncDomainWithMembership=1 [params.MS_TCPIP.Adapter1] SpecificTo=Adapter1 DHCP=No EnableAdapterDomainNameRegistration=No IPAddress=(IP Address) SubnetMask=255.255.255.0 WINS=No [params.MS_TCPIP.Adapter2] SpecificTo=Adapter2 DHCP=yes DNSServerSearchOrder=(DNS Address) EnableAdapterDomainNameRegistration=Yes WINS=Yes WINSServerList=(WINS Address) I removed all specific info (our company has a really strict policy on this stuff) so if anyone sees anything please help. I am pulling my hair out. Oh, and the Install Path and Reset Source paths are correct... for now, we will be changing that in the future. Thank you!

Unfortunetly even if the SATA Chipset is integrated into the SouthBridge you will still need drivers for it. Put the drivers in both WinPE and the install source, if you need any pointers check out http://unattended.msfn.org/intermediate/drivers/raid.htm This is the method I use to include my SATA drivers in my install source. Good Luck.

Install the WinPE OPK from the CD you have (onto a normal working computer running XP or 2K) and check out the help file. It has all the info you are requesting.

When building the PE Image (using mkimg.cmd) make sure your source directory is pointing to a Server 2003 CD (or folder) so that you get the Server 2003 files. They should not be too much different from the XP files but that would be the first thing I would try. Next, make sure you have the latest version of WinPE (1.2 I think) and the updated OPK will help with the new features. Just a couple of ideas...

It's alot easier to use the INI file. If memory serves me correctly it is ghost.ini. If you use that file then you don't have to worry about typos (on the command line). Just a suggestion :-)

I am sorry but you are not correct in all of you assumptions... I sell over 300 devices that are considered handhelds that run Win XPe, not CE becuase of their functionality. Then why doesn't MS make a gui tool to add features like Bart does? Because they don't want it to be easy to modify. I showed you in MS's own words that it was to make sure WinPE was not used as a pirated OS. That was my point on this matter. It is feature-less. It has no features except the recovery console in a Win32 enviroment. If you want Windows Scripting support, or HTA support you have to add it seperately, thus making WinPE feature-less... unless you add the features manually. (The way it was meant to be, I do not disupte this). I agree that there is no need to bring it to a consumer level, because the consumer is not the target audience. That is my point. It is by design too cryptic for the common customer (without any programming experience, or more extensive knowlege of how Windows works other than using it and configuring the minor settings). It's not a claim I came to by my own volition (excuse the sp errors), but a claim that has been supported by a few MCSE OEM Texts I have access to from work, and MSPSS Techs I have dealt with on issues concerning WinPE. I am sure we can debate on this forever, at this point I am agreeing to disagree about the situation. I feel that we both have twisted the subject of this thread and I only posted to publish my opinion. It is ok that my opinion based on my experiences with MSPSS and other texts is different than yours, in fact, difference is what keeps the IT industry moving forward... if we all agreed, we wouldn't have very many options to choose from (now, that comment can open up a whole new can of worms so I will leave it at that). Have a good one :-)

XP Embedded is a full version of XP that was componentized (if that is even a word) so that each component could be removed and the OS could be strictly customized and shrunk to fit customized hardware such as cellphones, pda type equipment, NAS, Hand-Held scanners, etc... WinPE was made to be cryptic, it was made for advanced users and MCSEs. BartPE was made for anyone who wanted to use it. If WinPE was made to be easy then there would be more tools for it other than mkimg.cmd. If you read my post completly you would have seen that I also identified the differences of both tools. (from my previous post) If M$ was not so worried about the use of WinPE Why would they impose such arbitraty Limitations to it... (this was taken directly from the OPK User's Guide) Because something was created for recovery and configuration does not mean it has to be feature-less or hard to use, it's the fact that Microsoft has a specific audience it has targeted to use this software, they provide additional resources for that audience... I should know, I am legally a part of that audience and I have been given access to other tools and documentation that has been helpful in my implementation of WinPE for system deployment to our clients. MS is a company, they want to make money, to do this they have to give tools to their larger clients to make deployment easier. WinPE is one of those tools.

WinPE is Hard to use for a reason. M$ does not want you useing it. It is only for OEMs who have an OEM "Support" contract with them and can get the specific tools and other documentation that makes using WinPE more economical. Since WinPE is a stripped down verion of XP, it has limits... But it still IS XP, so M$ does not want people using WinPE for their main OS. (Which would be tough, but I am sure someone (out of a million) would do it). BartPE is easier to use becuase it was made for everyone, not just a select group. So they are both good tools in their own way. I prefer a working copy of WinPE for dealing with Windows XP and Server 2003 Installs while I like BartPE for just about eveyrthing else. Just keep that in mind when trying to configure and creae a custom WinPE disc, it will be tough because M$ wants it that way.