RE: Unattended Install Dilemma
From: Darrell Gorter[MSFT] (Darrellg_at_online.microsoft.com)
Date: 05/18/04
- Next message: Tom: "Serious Problems"
- Previous message: sascha: "xp repair problems"
- In reply to: Jeff: "RE: Unattended Install Dilemma"
- Next in thread: Jeff: "RE: Unattended Install Dilemma"
- Reply: Jeff: "RE: Unattended Install Dilemma"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 16:48:13 GMT
Hello Jeff,
It isn't supposed to make any difference as to whether you use a batch file
or run via the commandline.
It isn't supposed to make a difference if you use a UNC or if you map a
drive letter.
I would suspect the UNC path versus the mapped drive letter, myself. I
cannot see just using a batch file causing the issue.
I presume you are getting the error during the Winnt32 phase of setup about
the product key?
What product key is accepted when you get this error?
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>Content-Class: urn:content-classes:message
>From: "Jeff" <Jeff_McCormick@decco.NOSPAM.com>
>Sender: "Jeff" <Jeff_McCormick@decco.NOSPAM.com>
>References: <e05001c43c10$4280ff30$a001280a@phx.gbl>
<laRfNJIPEHA.3800@cpmsftngxa10.phx.gbl>
>Subject: RE: Unattended Install Dilemma
>Date: Tue, 18 May 2004 05:22:51 -0700
>Lines: 120
>Message-ID: <e90101c43cd2$d69dc8c0$a501280a@phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcQ80tadJs52ZCKzS6KIrsUNJL6D5Q==
>Newsgroups: microsoft.public.windowsxp.setup_deployment
>Path: cpmsftngxa10.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.windowsxp.setup_deployment:111578
>NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>
>thanks for getting back to me darrell!
>
>as far as I can tell, the bat file is the SAME info that
>I am putting into the command line for winnt. my command
>line usually looks something like this (where E: is the
>mapped network drive) --
>
>winnt32 /unattend:E:\unattend.txt /s:E:\i386
>
>the bat file is the same, except instead of using mapped
>drive letters, it uses the UNC naming convention
>(\\Distrbution\windist\i386, etc) but it is doing the
>exact same thing. However, like I said, using the bat
>file doesnt give the Product Key error.
>
>we are upgrading win2k machines to winxp pro w/sp1
>slipstreamed into the distribution folder, with a volume
>license key and volume license media.
>
>I believe that I may have used the UNC addresses once
>with the winnt32 command, but I cannot remember if it
>worked or not. Even if it did, why would using the UNC
>method cause a problem with a product key? I would
>expect it would work or that it wouldnt work at all, as
>it wouldnt be able to find the proper files.
>
>- Jeff
>
>>-----Original Message-----
>>Hello Jeff,
>>What is in the bat file?
>>There shouldn't be any difference to running a
>commandline Winnt32 than
>>from running it inside a batch file from a mapped
>network drive.
>>you only need an upgrade key if you are using upgrade
>media.
>>What OS are you upgrading over?
>>How are you starting the upgrade? From a UNC or a
>mapped network drive?
>>What are all the swtiches that you are using?
>>Thanks,
>>Darrell Gorter[MSFT]
>>
>>This posting is provided "AS IS" with no warranties, and
>confers no rights
>>--------------------
>>>Content-Class: urn:content-classes:message
>>>From: "Jeff" <jeff_mccormick@decco_NOSPAM_.com>
>>>Sender: "Jeff" <jeff_mccormick@decco_NOSPAM_.com>
>>>Subject: Unattended Install Dilemma
>>>Date: Mon, 17 May 2004 06:10:00 -0700
>>>Lines: 37
>>>Message-ID: <e05001c43c10$4280ff30$a001280a@phx.gbl>
>>>MIME-Version: 1.0
>>>Content-Type: text/plain;
>>> charset="iso-8859-1"
>>>Content-Transfer-Encoding: 7bit
>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>>>Thread-Index: AcQ8EEKAEcDTqSzSRY20Ux5Vt+x8Hg==
>>>Newsgroups: microsoft.public.windowsxp.setup_deployment
>>>Path: cpmsftngxa10.phx.gbl
>>>Xref: cpmsftngxa10.phx.gbl
>>microsoft.public.windowsxp.setup_deployment:111481
>>>NNTP-Posting-Host: tk2msftngxa08.phx.gbl 10.40.1.160
>>>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>>>
>>>I recently posted the unattended setup problem below,
>but
>>>here is an update the problem --
>>>
>>>I have discovered that I am able to upgrade the client
>>>machines via the unattend.bat file that is
>automatically
>>>created with the distribution share on the server if i
>>>simply map the shared drive on the distrobution server
>to
>>>the client computer, then execute the said unattend.bat
>>>file. when doing this, instead of running a command
>from
>>>the DOS prompt, it completes the unattended upgrade,
>>>without complaining about an invalid product key. Any
>>>idea why running this process via the .bat file would
>>>work, and not the winnt32 prompt command? I have a
>winxp
>>>resource kit documentation book and it mentions nothing
>>>about using this .bat file, only winnt32.exe. It was
>>>only on a whim that I decide to try this, and lo and
>>>behold, it worked. Any ideas?
>>>
>>>- Jeff
>>>
>>>
>>>
>>>Previous Post--
>>>
>>>I've created a slipstreamed XP SP1 install from a
>server
>>>here at work, and set up the distribution folders in
>>>order to install/upgrade via unattended intalls.
>>>However, while testing this out using a freshly
>installed
>>>win2k on a laptop which i wish to upgrade to xp, it
>keeps
>>>telling me that the product key in tha answer file is
>>>wrong. Now, I know this key works, I've used this key
>>>for creating our Ghost Images for other machines, but
>it
>>>will not work for this unattended install setup. Does
>it
>>>need an upgrade product key instead? Or should this
>one
>>>work? I've tried several different keys, but none seem
>>>to be working. Any ideas?
>>>
>>>
>>
>>.
>>
>
- Next message: Tom: "Serious Problems"
- Previous message: sascha: "xp repair problems"
- In reply to: Jeff: "RE: Unattended Install Dilemma"
- Next in thread: Jeff: "RE: Unattended Install Dilemma"
- Reply: Jeff: "RE: Unattended Install Dilemma"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|