Thanks Keith. I can kick off the litetouch but when it gets to the task of
"Upgrade Windows" it fails with error:
<![LOG[Command completed, return code =
-2147467259]LOG]!><time="14:30:15.000+000" date="01-30-2017"
component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259
0x80004005]LOG]!><time="14:30:15.000+000" date="01-30-2017"
component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259
0x80004005]LOG]!><time="14:30:15.000+000" date="01-30-2017"
component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log
...\SMSTS.LOG.]LOG]!><time="14:30:15.000+000" date="01-30-2017"
component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property RetVal is now = -2147467259]LOG]!><time="14:30:15.000+000"
date="01-30-2017" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
Running the litetouch the console of the PC works fine and it upgrades
successfully, its just doing this remotely that is not working for some reason.
Dan Franciscus
Systems Administrator
Information Technology Group
Institute for Advanced Study
609-734-8138
From: "Keith Garner" <keith.gar...@hotmail.com>
To: mdtosd@lists.myitforum.com
Sent: Monday, January 30, 2017 12:01:00 PM
Subject: RE: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
(The “Correct” way to kick off a MDT Upgrade Task sequence remotely is through
Configruation Manager with ZeroTouch J .)
It should be possible to kick off a MDT Litetouch upgrade process remotely. If
you have psremote enabled, you could run a powershell script on the remote
machine. Make sure the MDT Deployment Server has the correct open permissions,
otherwise, you can kick off the command with the command:
Invoke-command -computer MyPC01 -credential $cred – scriptblock { Cscript.exe
\\server\deploymentshare$\Scripts\Litetouch.vbs /UserID:LabAdmin
/UserDomain:Corp /UserPassword:P@ssw0rd /TaskSequenceID:MyWin10Upgrade
/SkipWizard:Yes }
(the preceeding command line was written from memory, you should figure out the
correct command line arguments. #YMMV
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Daniel Franciscus
Sent: Monday, January 30, 2017 7:50 AM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
Does anyone use a powershell or psexec method to do this remotely? So far I
have not had success with this.
Dan Franciscus
Systems Administrator
Information Technology Group
Institute for Advanced Study
609-734-8138
From: "Sean Chapman" < schap...@coilcraft.com >
To: mdtosd@lists.myitforum.com
Sent: Friday, January 27, 2017 9:43:32 AM
Subject: RE: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
Ah yes I see, I had to actually google more to find out you were right about
having to be in the OS already. That is a little surprising but at least there
are powershell, login script, psexec, etc options to kick those off
automatically.
From: listsad...@lists.myitforum.com [ mailto:listsad...@lists.myitforum.com ]
On Behalf Of Daniel Franciscus
Sent: Friday, January 27, 2017 8:14 AM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
Hi Sean,
That link is the same article I posted. It doesn't show what you need to do
upgrade without being in the OS.
Dan Franciscus
Systems Administrator
Information Technology Group
Institute for Advanced Study
609-734-8138
From: "Sean Chapman" < schap...@coilcraft.com >
To: mdtosd@lists.myitforum.com
Sent: Friday, January 27, 2017 8:58:23 AM
Subject: RE: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
I don’t think this is true, you can definitely make an upgrade TS that pulls
the settings from 7 and does not have to be kicked off in the OS.
https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit
From: listsad...@lists.myitforum.com [ mailto:listsad...@lists.myitforum.com ]
On Behalf Of Daniel Franciscus
Sent: Friday, January 27, 2017 7:44 AM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
Great, at least I know now.
Thanks.
Dan Franciscus
Systems Administrator
Information Technology Group
Institute for Advanced Study
609-734-8138
From: "Marable, Mike" < mmara...@med.umich.edu >
To: mdtosd@lists.myitforum.com
Sent: Friday, January 27, 2017 8:27:57 AM
Subject: [MDT-OSD] RE: Using WDS and MDT to Upgrade to Windows 10
No, since the upgrade process will be grabbing settings from Windows 7 (what
apps are installed, use profiles, etc.) the upgrade has to start from within
the full OS.
Mike
From: listsad...@lists.myitforum.com [ mailto:listsad...@lists.myitforum.com ]
On Behalf Of Daniel Franciscus
Sent: Friday, January 27, 2017 8:10 AM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] Using WDS and MDT to Upgrade to Windows 10
Hi all,
I followed this article on using MDT to upgrade Windows 7 to Windows 10. My
question is, can I boot machines with WDS and PXE to run the upgrade task
sequence instead of running it from a logged on computer? When I attempt this
for some reason the window does not show the task sequence for upgrading at
all, it is blank. Although if I run the litetouch.vbs while logged into the
computer, it works fine just like in the article. Wondering if what I am trying
to do is supported.
https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit
Dan Franciscus
Systems Administrator
Information Technology Group
Institute for Advanced Study
609-734-8138
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be
used for urgent or sensitive issues
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The information contained in this communication and all accompanying documents
from Coilcraft may be confidential and/or legally privileged, and is intended
only for the use of the recipient(s) named above. If you are not the intended
recipient you are hereby notified that any review, disclosure, copying,
distribution or the taking of any action in reliance on the contents of this
transmitted information is strictly prohibited. If you have received this
communication in error, please return it to the sender immediately and destroy
the original message or accompanying materials and any copy thereof. If you
have any questions concerning this message, please contact the sender.
