Is there some known issue with new versions of winpe and slower multicasting? The server is 2016 1607. Winpe 1607 can multicast a computer in about half an hour, but newer versions take like 4 hours.
↧
multicast slower with winpe 1703-1809, but good with 1607
↧
multicast slower with winpe 10 1703 through 1809, but good with 10 1607
Is there some known issue with new versions of winpe and slower multicasting? The server is 2016 1607. Winpe 1607 can multicast a computer in about half an hour, but newer versions take like 4 hours.
↧
↧
Issue with default profile after capture
Hello,
I have a strange issue and I'm not sure what is going on. I create a reference image for Windows Server 2019, run Sysprep with my unattend.xml which has copy profile set to true. When I reboot the server I go through the oobe process and create a user and
the profile is created from default profile as it should be. To be sure I create another user with computer management and login in with that user. User profile loads fine with the default profile settings. So I assume my unattend.xml works and does the job.
However when I run the capture process and load the wim to another VM. All the customization of the default profile is gone.
Here is my procedure:
1. I log in with audit mode make all the customization and then I run sysprep /generalize /oobe unattend.xml. The unattend.xml has only copyprofile set to true.
2. Windows shutdown - I start the VM from PXE and run the capture process to create a WIM. Please see an image of my capture task sequence. I disabled all sysprep task.
It appears the capture process reset the default profile, but I'm not sure why.
Thanks
Edy from Switzerland
↧
Trouble booting To MDT, keep getting the command line
Hi,
When I try to boot to MDT to image a PC, it only gets as far as the MDT splash screen then goes to the command line, "X:\Windows\System32>". prompt. I think it may have to do with the LiteTouchPE_64 boot image, but I'm not entirely sure.
Any ideas?
Thanks
↧
Error using DISM to Mount Wim Image
For what used to work, now unmounting a WIM gives me an error stating that the path is invalid.
I can mount a WIM, modify the file, make sure I am not in the folder where the WIM is, before unmounting.
Dism /Unmount-Image /MountDir:C:\test\offline /commit
Error 161
The specified path is invalid.
That path is where the WIM did get mounted to. Also, now I cannot remove the offline folder. I renamed it and now I have 3 folders, test, test1 and test2 that I cannot remove and they are taking enormous space.
Any idea what's going on and how to delete the test/offline folders?
↧
↧
How to use MDT Applications for PDQ push requests
Recently, I was asked to limit the number of Task Sequences in MDT. We had a TS for every Office version, combined with some OS verions, so we had a lot of work when we changed something (copy every change to all task sequences).
Until now, we used the "Run Command Line" step to start single PDQ push requests, using the "Run this step as the following account" option. There we set the proper domain account and the installation was successful. We could add a number of these command line push requests and everything worked just fine. The command line we use:
cmd /c \\PDQServer\Deploymentshare$\Scripts\psexec.exe \\PDQServer -u domain\user -p Password -h -accepteula "c:\program files\Admin Arsenal\PDQ Deploy\pdqdeploy.exe" Deploy -Package "PDQ Package name" -Targets %Computername%
To limit the number of TS’s, I had the idea of using MDT applications. There you can select the applications you want to install during the Deployment Wizard. So I went ahead and created some applications using the same command line as above. I didn’t set a working directory. In customsettings.ini I added the line: SkipApplications=NO
But I ran into a problem: The MDT Task sequence runs with the local administrator, and that account is not allowed to connect to our domain joined PDQ server. The "Install Application (Install multiple installations)" step has no option to run as a different user. Although the domain user was included in the command line, it simply didn’t work. Result: no software was installed. My first approach was changing the logged on user so the task sequence could continue with the needed permissions. That didn't work as expected either, the task sequence did not continue after login.
Now the solution:
The "Install Application" step launches ZTIApplications.wsf script. So at first, I replaced the standard "Install Application (Install multiple installations)" step by a "Run Command Line" step that launches the same script:
Command line: cscript \\PDQserver\deploymentshare$\scripts\ZTIApplications.wsf
Start in: \\PDQserver\deploymentshare$\scripts
Run this step as the following account: domain\user
I also checked the "Load the user's profile" box.
That also didn’t do the whole trick. Now I was missing the Application page in the deployment wizard…
So, after the command line created in the step above, I added the normal "Install Application (Install multiple installations)" step again.
Eureka! Now I have the select application page back, ZTIApplications.wsf will be launched a first time as the domain user, and install everything I selected. After that ZTIApplications.wsf will be launched for a second time as the local administrator, but it won’t try to install any software again, as everything was already installed. The BDD.log file shows this:
“Application {1fa07a58-6aaf-4a1c-82c7-06a8a100e09c} has already been installed, will not install again.”
Maybe a last tip. You can already check some applications in the list, if you add the Application GUID in customsettings.ini. For example:
Applications001={1fa07a58-6aaf-4a1c-82c7-06a8a100e09c}
Applications002={4f7f5190-3f9c-44d5-9f37-0b600a399b0d}
If you want some applications to be mandatory (so the can't be unchecked):
MandatoryApplications001={1fa07a58-6aaf-4a1c-82c7-06a8a100e09c}
MandatoryApplications002={4f7f5190-3f9c-44d5-9f37-0b600a399b0d}
That’s all, enjoy!
↧
command line during deployment to Surface Book 2
Hello,
Well I think I'm finally starting to understand DeploymentWorkbench! I have built a few HP EliteDesks but am running into a challenge with my Surface Book 2. I created the "Set Task Sequence Variable" for the out of box variables but for some reason it doesn't seem to be working and I'm not sure why. I made the Value "Windows 10 64-bit\%Make%\%Model%" to correspond to my folder names but after the OS deployment it just dumps me to a command prompt and doesn't seem to have installed the drivers. How can I tell why this isn't working?
Thanks!
↧
MDT bitlocker is writing the key to c:\ drive
Hello
Is this a normal behavior that MDT writes the key to c:\ drive into a text file ?
thanks
↧
Office Deployment
Hi Guys
Am new to using MDT so apologies if this is a stupid question :-)
I am looking to deploy Office2013 using as an application as part of my OS deployment, but the Office configuration may be different depending on where the machine is being deployed - so some will have a small set of apps installed, others may have the full suite.
I created and MSP file for the small set of apps and deployed that and it worked fine, created another MSP to do the full install - how do I get to specify or choose which MSP file should be used during each deployment ?
Sorry if thats not clear.
Thanks
Garry
↧
↧
USMT - Migrate ALL settings
I set up a couple of new Server 2016 servers and a new Windows domain. I don't want to upgrade the existing domain since it's already upgraded a couple of times, and the domain name is incorrect. So that's all fixed with the new servers and new domain. As a result, the client PC's, mostly Windows 10, have to switch to the new domain. No problem. Same for the users. Ah - a new domain means a new user profile. Okay for those who like a fresh start. But for those who want to keep their current profile, I'm trying to export / import those with USMT. Since I would like to 'migrate' ALL settings, I created a XML file like this:
<?xml version="1.0" encoding="UTF-8"?><migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/migautodesk"><component type="System" context="User"><displayName _locID="miguser.everything">everything</displayName><role role="Settings"><detects><detect><condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_APPDATA%")</condition></detect></detects><rules><include filter="MigXmlHelper.IgnoreIrrelevantLinks()"><objectSet><pattern type="File">%CSIDL_APPDATA%\* [*]</pattern><pattern type="Registry">HKCU\SOFTWARE\ [*]</pattern></objectSet></include><locationModify script="MigXmlHelper.RelativeMove('%CSIDL_APPDATA%','%CSIDL_LOCAL_APPDATA%')"><objectSet><pattern type="File">%CSIDL_APPDATA%\* [*]</pattern></objectSet></locationModify></rules></role></component></migration>The command line:
scanstate /i:everything.xml /l:scanstate_%computername%.log \\server\d$\mystore /ue:*\* /ui:domain\user /o /localonly
No errors exporting and importing.
This works partially - not all settings are exported / imported. I also notice a bunch of folders located in the original user profile underRoaming appdata now appear under Local appdata in the target folder.
I take it my approach is way too simple to work, so I wonder what to do to migrate all user settings from domain X to domain Y?
Simon Weel
↧
How to upgrade MDT integrated with SCCM
Hi Team,
My organisation wants me to upgrade SCCM from v1706 to v1802 and for imaging purpose we have MDT integrated.
I would like to know :-
1. How to upgrade MDT and which version is compatible with SCCM 1806
2. Would there be any impact if I upgrade MDT on boot images and existing images ?
↧
Updated my boot wim - Everything looks different and doesn't show my images. Trying to go from Win8 ISO boot.wim to WIn10 ISO boot.wim. Need help....
Hi folks. I believe my original boot.wim that I have been using for years was based off of a Windows 8 or 8.1 ISO and I just added drivers to it when I had to. I just now tried to make a new boot image using a Windows 10 ISO because we're having issues on some models with a red line appearing right after the centered Windows logo after it loads up the boot.wim. That's for another thread I think though. I'd like to use the Windows 10 based boot.wim but I don't know why everything is completely different now. Also it prompts for login info right after the Windows logo splash screen which it didn't do before and then when it gets to the image list it only lists 1. I have probably 100 images when I boot to the old Windows 8/8.1 boot image that I've been using.
Pictures attached of my working setup and after when trying to use the Windows 10 boot.wim. It's been so long since I originally set this up I don't know if there are other steps I have to do to use an entirely different boot image. Thank you!
FIRST 2 Pics are using the new WINdows 10 ISO that doens't really work as it prompts for login info and only shows me one old image
SECOND PIc is the splashscreen of my fully functional Win8/8.1 based boot image.
↧
Red Vertical line right after Windows Splash screen during WinPE Boot
Hi Folks. We are randomly having issues with laptops that boot to the boot.wim, get to the Windows splash screen with spinning circle but then immediately go to black screen with red vertical line (picture attached). After that nothing happens
like it froze. Really need help figuring this out. Thanks!![]()
↧
↧
MDT 2013 Update 3 Rule.ini for each task sequence
I need some help in getting this figured out. I have a task sequence call XX-001. I want to use the XX.ini for its rule. Adding a line to display the apps.
In the TS I added %DeployRoot%/Control/XX.ini for Gather in all three places .
Still I am not able to get the applications list displayed. Any suggestions?
This is my XX.ini looks like.
[Settings]Priority=TaskSequenceID,Default
Properties=MyCustomProperty
[XX-001]
_SMSTSORGNAME= XX - %TaskSequenceID%
TaskSequenceID=XX-001
SkipApplications=NO
SkipSummary=NO [Default]
_SMSTSORGNAME=XXXX- %TaskSequenceID%
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
OSDComputerName=ABC-%SerialNumber%
AdminPassword=XXXXXXXXX
HideShell=NO
SkipComputerName=NO
DoNotCreateExtraPartition=YES
ApplyGPOPack=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=NO
SkipFinalSummary=NO
TimeZoneName=Eastern Standard Time
↧
MDT Deployment for 1903
Hi all,
Has anyone managed to successfully use MDT to upgrade from 1809 -> 1903.
Every time I try to deploy it, I get an error.
ZTI Heartbeat: command has been running for 1 minutes (process ID 1072) LTIApply 30/08/2019 10:22:04 0 (0x0000) Event 41003 sent: ZTI Heartbeat: command has been running for 1 minutes (process ID 1072) LTIApply 30/08/2019 10:22:04 0 (0x0000) Console > Error: 0x800f0818 LTIApply 30/08/2019 10:22:14 0 (0x0000) Console > DISM failed. No operation was performed. LTIApply 30/08/2019 10:22:14 0 (0x0000) Console > For more information, review the log file. LTIApply 30/08/2019 10:22:14 0 (0x0000) Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log LTIApply 30/08/2019 10:22:14 0 (0x0000) Return code from command = -2146498536 LTIApply 30/08/2019 10:22:14 0 (0x0000) FAILURE ( 5627 ): -2146498536 0x800F0818: Run DISM.exe LTIApply 30/08/2019 10:22:14 0 (0x0000) Event 41002 sent: FAILURE ( 5627 ): -2146498536 0x800F0818: Run DISM.exe LTIApply 30/08/2019 10:22:15 0 (0x0000) Command completed, return code = -2147467259 LiteTouch 30/08/2019 10:22:15 0 (0x0000) Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 30/08/2019 10:22:15 0 (0x0000) Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 30/08/2019 10:22:15 0 (0x0000)
Above is the error I get, I've tried the new ADK, I've tried the previous ADK.
I've also tried disabling the upgrade packages because sometimes MDT would attempt to update to 1809 packages after installing 1903. If anyone has any ideas please let me know.
Kind regards,
Haydon
↧
WDS2010 - PXE-E55 ProxyDHCP service did not reply to request on port 4011
Hello - I have read through just about every thread with no luck. My imaging server was working perfectly fine up until a a couple days ago. Now, when I try to PXE boot I get the error "PXE-E55 ProxyDHCP service did not reply to request on port 4011". No configuration changes have been made to the server.
I do not believe I am using DHCP because in the Multicast settings it specifies a range of IPs. I am not using the Auto-Add policy. It is set to Answer clients. I have stopped and started WDS services as well as reboot the server. Even disabled the firewall to see if that did anything. Not sure what else to try.
Here is my configuration:
CONFIGURATION INFORMATION FOR SERVER[-----------------------------------------------------------------------------]
Server Authorization:
Authorization state: Not Authorized
Answer Policy:
Answer clients: Yes
Answer only known clients: No
Response delay: 0 seconds
Active Directory Use Policy:
Preferred DC:
Preferred GC:
Prestage devices using MAC: No
New computer naming policy: %61Username%#
Domain search order: Global Catalog Only
New computers join domain: Yes
New Computer OU:
OU type: Server Domain
OU: CN=Computers,DC=domain,DC=rpcs,DC=org
DHCP Configuration:
DHCP service status: Not Installed
DHCP option 60 configured: <Not Applicable>
PXE Bind Policy:
Use DHCP ports: Yes
Rogue detection: Disabled
RPC port: 5040
Interface Bind Policy:
Policy: Exclude Registered
Registered interfaces:
Boot Program Policy:
Known client PXE prompt policy: OptIn
New client PXE prompt policy: OptIn
Allow N12 for new clients: <Not Applicable>
Architecture discovery: Enabled
Reset boot program: No
Default boot programs:
x86 - boot\x86\pxeboot.com
x64 - boot\x64\pxeboot.com
ia64 - boot\ia64\bootmgfw.efi
Default N12 boot programs:
x86 - boot\x86\pxeboot.n12
x64 - boot\x64\pxeboot.n12
ia64 - boot\ia64\bootmgfw.efi
Banned GUIDs list:
Boot Image Policy:
Default image type for x64 clients: Both
Default boot images:
x86 -
x64 -
ia64 -
WDS Client Policy:
Logging policy:
Enabled: No
Logging level: Info
Unattend policy:
Enabled: No
Command-line precedence: No
WDS unattend files:
x86 -
x64 -
ia64 -
OSChooser Policy:
Menu name:
Server Automatic Refresh Policy:
Refresh period: 900 seconds
BCD Refresh Policy:
Enabled: No
Refresh period: 60 minutes
Auto-Add Policy:
Policy: Disabled
Poll interval: 10 seconds
Max retry count: 2160 times
Message to pending clients:
Retention period:
Approved devices: 30 days
Other devices: 1 days
Defaults for x86:
Referral server:
Boot program path:
WDS client unattend file path:
Boot image path:
User: Domain Admins
Join rights: Full
Join domain: Yes
Defaults for x64:
Referral server:
Boot program path:
WDS client unattend file path:
Boot image path:
User: Domain Admins
Join rights: Full
Join domain: Yes
Defaults for ia64:
Referral server:
Boot program path:
WDS client unattend file path:
Boot image path:
User: Domain Admins
Join rights: Full
Join domain: Yes
WDS PXE Providers:
Name: VMMOSDProvider
Path: C:\RemoteInstall\DCMgr\bin\OSDPxeProvider.dll
Order: 1
Critical: Yes
Name: BINLSVC
Path: C:\Windows\system32\binlsvc.dll
Order: 2
Critical: Yes
WDS Transport Server Policy:
IPv4 source: Range
Start address: 239.0.0.1
End address: 239.0.0.254
IPv6 source: Range
Start address: FF15::1
End address: FF15::FF
Start port: 64001
End port: 65000
Network profile: <Not Applicable>
Multicast session policy:
Slow client handling policy: None
AutoDisconnect threshold: 256 KBps
Multistream stream count: 2
Slow client fallback: Yes
[-----------------------------------------------------------------------------]
Does everything look right? The previous systems administrator set this up so I am not totally familiar with it. Thanks in advance for any help you can provide!
-Mike
↧
MDT 2013 USMT Replicate Task Sequence Error 41002 FAILURE 5456
Hi Guys,
I am trying tot setup USMT to capture user profile and store onto a share. I have setup a Replicate TS and when testing on a VM it captures the user profile into a usmt.mig on the share fine, but when I test on a physical device I get:
FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.
Event 41002 sent: FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.
Litetouch deployment failed, Return Code = -2147467259 0x80004005
I have tested on windows 10 Build 1709 and Build 1607 to no avail. These are on Lenovo laptops with a single HDD and partition.
Any assistance would be wonderful!!
Thanks,
Mark.D
↧
↧
Fail to detect partition via GetOSTargetDriveLetter during ZTIUserState Capture
Hoping to get help from the experts. I have an MDT 2012 Update 1 share that I've been using for a while in which I have support to USMT offline. The media that I build off it have all worked in the past. Recently for some unkown reason I have started getting failures within the USMT offline portion of the task sequence. If I bypass the USMT portion the deployment goes thru without a glitch. I've tracked down the failure to be within the GetOSTargetDriveLetterEx function in ZTIUtility. Looks like we're not able to determine the OS partition but I can't figure out what I need to do to resolve this. The below log is the standard ZTIUserState log with added lines so I can check variables. The lines in bold are simply oLogging entries to print out variable values but as you can see most of the are empty. Any help is greatly appreciated
Property capture is now = Microsoft Deployment Toolkit version: 6.1.2373.0 The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. Inside GetOSTargetDriveLetterEx OriginalPartitionIdentifier= DestinationOSRefresh= OSDTargetDriveCache= ScriptName=ZTIUserState TargetPartitionIdentifier= DestinationOSInstallType=ByVariable DestinationOSDriveLetter= DestinationOSVariable= bDiskPartFound=True DestinationOSInstallType=ByVariable DestinationOSInstallType=ByVariable DestinationOSDriveLetter= DestinationDisk=0 DestinationPartition=1 Unable to yield a target Partition (Special Recovery option for Litetouch). DestinationDisk and Partition did not yield a target Partition. FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.
↧
MDT USMT5离线刷新
使用MDT USMT5自动迁移备份工具。默认情况下，可以在用户界面中使用LiteTouch仅备份域用户的数据。但是，在WinPE模式下，无法备份域用户数据。有什么方法可以解决这个问题吗？
↧
Computer naming
Hi
I'm quite new to MDT (and for that matter WDS) and I've having two distinct issues.
The first revolves around the Computername or OSDComputername.
If I prompt for a computername prior to installation I can set what I want, eg 1234 and this will be used in the logging written back to the MDT logs folder. However when the machine is imaged it seems to come back with a random computername, of Desktop-xxxxx. So I'm wondering what is missing in the process?
What I'd really like however is a custom prompt to input the asset tag number and then build the Computer name from that, for example, out convention should be if a Desktop, DT+asset tag and if a laptop LT+asset tag. For example I use LT1345.
Is there anyway of creating a custom prompt and then appending that to a prefix based on device type? I found some suggestion online using the code (extracts) below but it doesn't seem to work for me.
[Settings]Priority=ByLaptop,ByDesktop,Default
[ByLaptop]
SubSection=Laptop-%Laptop%
ComputerType=LT
[ByDesktop]
SubSection=Desktop-%Desktop%
ComputerType=DT
[Default]
OSDComputername=%ComputerType%
As above though, this is only part of what I'd really like it to look like.
↧