sysprep help

Nikumba · 3 Aug 2011 at 11:25

Hi all,

Trying to build a sysprep file, and having a few problems with it, I have set the activation proxy in it, however it does not seem to be working, when it auto logson it says there is a problem with the licence and needs to activate it, then will eventually prompt for the proxy box, enter that and it will all work, however I believe this should be done all automatically, anyone suggest what is not working correctly?

Unless someone knows the domain/IP that XP talks to for activation and I can set up routing on our network for it.

Thanks

Kimbie

************ = Company identifying marks,

Code:

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    InstallFilesPath=C:\sysprep\i386
    Autoactivate=Yes
    AutoactivateProxy=Proxy
    TargetPath=\WINDOWS
    ActivateProxy=Proxy

[GuiUnattended]
    AdminPassword="************"
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    TimeZone=85
    OemSkipWelcome=1
    AutoLogon=Yes
    AutoLogonCount=2

[UserData]
    FullName="************"
    OrgName="************"
    ComputerName=103till5

[Display]
    Xresolution=1024
    YResolution=768

[TapiLocation]
    CountryCode=44
    AreaCode=01733

[RegionalSettings]
    SystemLocale=00000809
    UserLocale=00000809
    InputLocale=0809:00000809

[Identification]
    JoinWorkgroup=************

[Networking]
    InstallDefaultComponents=Yes

[Proxy]
    Proxy_Enable=1
    Use_Same_Proxy=1
    HTTP_Proxy_Server=activation.************.co.uk:8000
    Proxy_Override=<local>

[Branding]
    BrandIEUsingUnattended=Yes

[GuiRunOnce]
    Command0=c:\inst\run.bat

chrislip · 4 Aug 2011 at 22:55

What version of XP are you using? OEM, retail or VLK?

Terrier_Jimlad · 6 Aug 2011 at 08:38

Tried adding the XP key under UserData as part of the sysprep file above?

ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

ubermik · 7 Aug 2011 at 08:57

I'm probably a bit of a beginner compared to other posters on here so apologies if this ends up just sounding like noob blather lol

But as its asking for validation doesn't that mean it cant be the VLK version?

I think the XP autoinstall is needlessly complicated. I tend to just use the CD install mainly which requires the winnt.sif. But remember skimming the instructions and for a share based install theres a different file name, and for adding network settings it creates one or two other files too

So a few things spring to mind

1. would you be REALLY badly breaking the rules if you just used the VLK/MSDN version of the same OS instead so validation wasnt needed?

2. If I recall properly the network settings are stored in a different file depending on install method I think theres maybe 5 or more different xxxxx.sif files for various things and different types of install some just being the same file given a different name depending on install method or stored in a different place

When extra files are used like for networking they have to be referenced in the initial files. So I know its obvious, but have you checked for typos and that all files are in the correct place for the type of intall?

3. Have you tried just getting known working files and editing them by hand? If you dont change much you could even automate creating a new one with a simple dos batch file and create it on the fly

4. Isnt there an optional switch to forego the validation that can be added to the scripts?

5. if all else fails, have you looked into using registry keys for the network settings dufing the GUI portion of the install to just blast the settings you want in if you cant get the scripted version to work?

Apologies if these are "silly" suggestions

Mike