Hi All,
I have an application name as anyconnect i just add in application but its not able install i think something is missing in its command line.
↧
How to Add and install application
↧
USMT Windows 10 MDT 2013 running Update 1 (also tried update 2) SCCM UDI creating profile: Win32Exception: There was an error while calling CreateProfile.: The system cannot find the file specified.
I get the following error message trying to run USMT restore se error below. I have checked the registry and profile list key and the user is not present before running USMT. Running in debug mode (f8 in SCCM winpe) i can see that the user are created in the registry profile list. If i run the USMT restore command manually after the user is created in the registry profile list USMT runs without error. If i delete the user from the registry profile list it fails with the same error message as below. In the task sequence "restore user state" i have tried running restore all captured profiles and customize how user are restored.
[0x080000] There was an error while calling CreateProfile. Error: 0x80070002
Error 2147942402 creating profile: Win32Exception: There was an error while calling CreateProfile.: The system cannot find the file specified.
creating profile: Win32Exception: There was an error while calling CreateProfile.: The system cannot find the file specified. [0x80070002
[0x000000] Failed.[gle=0x00000006]
The system cannot find the file specified.[gle=0x00000006]
[0x000000] * USMT error code 71:
[0x000000] | A Windows Win32 API error occurred
[0x000000] | Windows error 2147942402 description: The system cannot find the file specified.
↧
↧
How to rename local administrator account when deploy Windows 7 image?
I am using MDT 2010 to deploy Windows 7 image. The image deployed fine and before I capture the image, I renamed local administrator account but the captured image reverse back to default administrator account?
Thanks for any help!
Ying
↧
netbios support in windows 10 adk, mdt 2012 update 1 and udi
Hi All,
Recently we upgraded our sccm osd imaging environment to sccm 2012 r2 cu4 with mdt 2013 update 1 and windows 10 adk. After we made this change we cannot use our the netbiosadomainname\username successfully in our udi wizard process to build a workstation. We have found however we can use FQDN\username in our udi wizard without issues.
Is this a change made in windows 10 adk? was support for netbios removed/dropped? and if so why?
Is this is the case and support for netbios has been turned off is there a way to turn that support back on, even it requires creating new boot images.
Any help is greatly appreciated
Cheers
Greg Turnbull
↧
Join Custom workgroup and Change Local administrator password
MDT 6.3.8330.1000 , ADK 10, windows 10 enterprise
Hi,
I have few request to create custom image to join workgroup name like WRK123 with local administrator password P@ssw0rd123.
I have setup my customsetting ini
SkipDomainMembership=YES
SkipAdminPassword=YES
AdminPassword=P@ssw0rd123
joinworkgroup =
WRK123
But everytime it join workgroup, uses as Workgroup and different password.
I have also change unattend.xml file for password under
7 oobeSystem > amd64_Microsoft-Windows-Shell-Setup__neutral_31bf3856ad364e35_nonSxS >userAccounts>adminsitratorPassword. no luck.
any thoughts??
orion
↧
↧
Golden Image unable to join domain through MDT rule
Hi,
I am using MDT 2013 for Windows 8.1 deployment.
All Works fine.
I just change my plan to deploy image instead of installing bare metal , i just capture golden image from one of my local machine and added in Operating system and creates its tasks sequence every thing works perfectly fine in RULE i just add machine should join domain but machine is unable to join domain or when i change its name it won't changes
here is my rule
[Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipBDDWelcome=YES SkipDeploymentType=YES SkipDomainMembership=NO JoinDomain=xxx.xx DomainAdmin=xxxx.xxxx DomainAdminDomain=xxxxx.xx DomainAdminPassword=xxxxxxx MachineObjectOU=OU=WSUS-HO-Computers,DC=csaplho,DC=pk SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=YES
↧
Windows 10 In-Place upgrade via MDT
Hi Guys,
I'm still searching for the best way to go about upgrading about 200 user computer from Windows 7 Ent to Windows 10 Ent (most of which I don't have physical access to). This is my first time working with MDT, and I still believe an MDT task seq can do exactly what I need it to do, simply upgrade the machine OS, I don't need anything else. All my users are local administrators on their respective machines and I was simply going to have them run litetouch.vbs and have it fully automated from there the only problem seems to be that when they log back in with their user account they are prompted "Wizard Error: You must be running with Administrator rights. The deployment cannot Proceed." (even thought they are set as a local administrator on the machine) and the task fails although windows has been upgraded to windows 10. The same thing seems to happen even when running lightouch as the domain admin. From what I gather upon upgrade of the OS you must login in as the actual .\administrator account which is currently set different on each machine for the task to complete. I've tried using the "administrator password" wizard panel in MDT which should set the administrator password to something of my liking but it doesn't seem to change the current password. What would be the easiest way to set this up to have my end user simply run a file to upgrade their OS? Is there any way to have the task sequence not require the final login after the OS has been upgraded already as the OS seems to function however the prompt that the sequenece failed comes up after every reboot until you log back in as .\administrator. Is there some easier way to do this outside of MDT? Thanks so much!
EDIT: A tool such as this for Enterprise would be exactly what I would be looking for, unfortunately it does not seem to be compatible for Enterprise: https://www.microsoft.com/en-us/software-download/windows10
↧
new to MDT - Task Sequence not showing up
i build my deployment share and add my Win10 (1511) OS then i build my Laptop and created a capture
- i created a Task Sequence to deploy my captured image but when i boot my laptop to PXE boot it just continually reboots just before my Task Sequences shows up
- if i press F8 i can ping my MDT server
Please help
↧
MDT 2013 Update 1, In-Place Upgrade to Windows 10. Blank screen and autologin not working
Hi,
I have domain joined clients running Windows 7 and 8.1 Professional, and I am trying to upgrade them to Windows 10 Professional.
I am doing the majority of the testing on a Hyper-V Virtual Machine running Windows 7 Professional, Retail product key activated. However the issues I am facing are also occurring on a couple of Dell test machines which have either Windows 7 or 8.1 OEM license. I must state, that performing a manual upgrade using the setup.exe (from the MDT Share\Operating Systems folder) does not cause the problems I am about to describe, this is MDT 2013 specific. I am using the standard upgrade client task sequence
- Firstly, the upgrade seems to go fine up until the last stages. It goes through the “Upgrade Windows” phase but gets stuck on this. I get the big circle which shows the upgrade percentage, then the screen which states something along the lines of “It’s taking a bit longer than usual, but it should be ready soon” and then suddenly a black screen – this happens on a VM and on physical machines, so I doubt it’s anything to do with graphics problems. I had left the VM like this for probably around 3 hours yesterday and it was still the same so I was kind of forced to reboot it but it didn’t make any difference, it continues with the “it’s taking longer than usual” message then black screen. The only way I can get into the system is by using RDP, after that I can then reboot it fine and it will give me the login screen like it should without the blank screen
- Once I can RDP into it, the task sequence continues but I have two scenarios:
- If I login using a local admin account (this is the most ideal one to use rather than a domain admin as we try to keep our clients as clean as possible by having a local admin (not called administrator we rename it) and just the domain users who use the PC), I get the error message “You must be logged in using an administrator account. The deployment cannot proceed”. I am assuming this is because it needs access to the MDT UNC share which a local admin account doesn’t have (though I have no idea why it isn’t using cached credentials since the execution of the vbs script is run using the domain admin credentials but initiated from the local admin windows login). This also leaves the MININT and _SMSTaskSequence folders on the local machine
- If I log in as a domain administrator then the task sequence continues and finishes successfully, however this login is not automatic even if I put the credentials into the unattend.xml file OOBE Phase (I notice that my credentials I put in here just seem to get overridden by a random password, I assume MDT is doing that at some point), I have to manually login to finalise the deployment
These are the only two issues I have remaining now, the black screen and automatic login to finish the process. I doubt I could put anything in the task sequence to help this as the monitoring of the deployment indicates that it is still on the “Upgrade Windows” phase.
I’d appreciate any help with this, anyone had similar issues?
Thanks
Steve
↧
↧
MDT 2013 deployment failure 5624
HI All
Have built a new MDT 2013 server upon a windows 2012 box, currently getting the following error when deploying Windows 7 image only all Win 8.1 and 10 images deploy fine. Can any one help with ?
FAILURE (5624): 1392 Run DISM: /Apply-
Image /ImageFile:\\HUYTONSC\DeploymentShare$|Operating Systems\Win 7 x32 Sp1 July 2015\Win 7 x32 Sp1 July 2015.wim index:1 /ApplyDir.F:
Litetouch Deployment Failed, Return Code -2147467259 0x800004005
Have tested the same images on a MDT 2010 server running Server 2k8 and also in a lab setup before hand and they all performed as expected and deployed fine.
Applied the MDT 2013 update 2 hoping that would resolve but it didnt, have also deleted and re added the images they work for 1 deployment and then fail there after
Banging my head on the table right now
Cheers
↧
Office 2016 (Volume Licencing Installer & ODT)
Hello, I am currently having issues installing Office 2016 with MDT using the ODT.
I get the following errors.
returned an unexpected return code: 110
returned an unexpected return code: 30088
I am also using an MSP file in the update folder just FYI this runs with no issue when clicking on Setup.exe manually.
Alex Olver
↧
Add a custom variable to MDT using PowerShell
Simple question. How to add a new custom variable to MDT using PowerShell? I only know how to do it from VBS.
↧
dirty environment
While end of install, the setup starts deploying apps, first apps name comes on the install and then, the setup does restart.
Then comes up. dirty environment, do i wanna start over or not and i click no, and then it starts again with the first app that made restart and goes on, installing them on fresh "client" computer. And then installs them on, no errors or warnings
So, how or what do i need to do to remove that dirty env problem and restart(Guessing the restart makes it "dirty")?
I changed the app in task seq but still same, i also removed and added again the first app, same. So, whats with the random restart just before/during first app install?
BDD log : https://onedrive.live.com/redir?resid=8F390ABF958ECF54!2105&authkey=!AFtfuTXTIsIzQNU&ithint=file%2clog
↧
↧
Windows Recovery Wizard
I am trying to get the Run the Windows Recovery Wizard option to appear at the Welcome Menu for my LiteTouch boot media. I have never had this option appear but now I would like to have it for convenience. I am deploying Windows Server 2012 R2 and Windows 8.1 in my environment. I mostly deploy via PXE boot using WDS, but I sometimes use the ISO image when necessary.
I started out with MDT 2013 and Windows ADK for Windows 8.1. I have upgraded to MDT 2013 Update 1 and Windows ADK for Windows 10 during my troubleshooting. My understanding of the circumstances in which the Windows RE option appears at the Welcome Menu is shaky, but from what I've read, it's determined by the winpe.wim from ADK or boot.wim from the OS that is selected by the MDT Workbench when updating the deployment share. Here is what I have tried so far.
- Added the most recent Windows Server 2012 R2 and Windows 8.1 OS's from the source files to the Deployment Workbench in an attempt to have MDT use those boot.wim images to build the WinPE image. Originally, all my deployment images were stored in WDS.
- Added the RTM versions of the OS's to the Deployment Workbench. (I read this was an issue in MDT 2012, but has since been resolved, so I didn't expect this to be the fix.)
- Replaced the winpe.wim file in the C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us folder with the boot.wim image from Windows Server 2012 R2. Doing this caused MDT to use the boot.wim image from my Windows Server 2012 R2 OS source folder and successfully built a bootable LiteTouchPE_x64.wim/iso image, but there is always an error message that an existing deployment is in progress when the deployment wizard begins.
Does anyone know if it is possible to display the Windows Recover Wizard option for a LiteTouch deployment using MDT 2013 Update 1 and Windows ADK 10, and if so, what I might be doing wrong?
↧
Windows 10 update Admin Account
Hi,
I am trying to update our workstation to windows 10. I have created an update task sequence and it run perfectly fine.
The only issue I have is regarding the final few stage where it tries to log in after reboot. We have the local admin account disabled by default and a new local admin account is create instead. So after reboot it tries to login and fails. I have edited the unattended file and added the other user but its made no difference.
<AutoLogon><Enabled>true</Enabled><Username>Admin2</Username><Domain>.</Domain><Password><Value>password2</Value><PlainText>true</PlainText></Password><LogonCount>999</LogonCount></AutoLogon>
↧
MDT Wizard - Skip unwanted deployment pages
Guys, I'm trying to skip unwanted deployment pages in my MDT Wizard. It seems the very first screen works, but once I click NEXT, the entire list of pages are showing and it makes me walk through each one.
I minimized my Bootstrap.ini and CustomSettings.ini
I only want to show the following pages;
- Task Sequence Page
- Computer Details Page
- Local and Time Page
- Ready Page
But for some reason after I click the Task Sequence, I receive this list. Then I have to go to each page without the ability to skip.
- Welcome Page
- Network Credentials Page
- Task Sequence Page
- Computer Details Page
- Mover data and settings Page
- User Data (Restore) Page
- Local and Time Page
- Capture image Page
- Ready Page
Customsettings.ini and Bootstrap.ini
[Settings]Priority=Default
[Default]
SkipBDDWelcome=NO
SkipTaskSequence=NO
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipComputerBackup=YES
SkipProductKey=YES
SkipPackageDisplay=YES
SkipLocaleSelection=NO
SkipTimeZone=NO
SkipRoles=YES
SkipApplications=YES
SkipAdminPassword=YES
SkipAdminAccounts=YES
SkipCapture=YES
SkipBitLocker=YES
SkipSummary=YES
SkipFinalSummary=NO
↧
Windows 10 Enterprise (x64) freezing during sysprep
I recently updated my MDT to Update 1 in order to start experimenting with a Windows 10 image however the following happens:
Windows 10 Enterprise base .wim installs. Goes to capture and on the 'Processing generalize phase SysPrep plugins' the capture
just freezes. No idea what is happening and there is nothing in the logs. Simply frozen.
So I installed U2 to see if that fixed it. Nothing. Still freezes.
This is with my MDTBuild share. My MDTDeploy share works fine and deploys our Win7 image without issues.
I am using HyperV 2012r2 to create the image so can delete and start again, but this is the third time the crash has happened.
Has this happened to anyone else?
Gareth
↧
↧
Manual Capture of Windows 10 ImageX DISM
For our Windows 7 reference images, I have created a WinPE ISO with imagex and captured the image which was then imported into MDT. I wanted to know if this manual procedure stays true for Windows 10>? I don't want to create a task sequence for capture. I am interested in a manual approach. I can't find good documentation on how to perform this via DISM manually.
I would appreciate some direction or guidance. Thank you!
↧
[MDT2013 Update 1] Task sequence not appearing when I pxe boot litetouch.wim
I've created a windows 10 standard task sequence but it wont appear when I pxe boot litetouch.wim
The deployment share I'm creating this in was originally created in MDT2013, when I imported this deployment share into update 1 I ticked the upgrade option.
Is there something obvious I'm missing here? I have checked the windows 10 task sequence and it's enabled and not configured to be hidden in the task sequence.
I have also tried deleting it and recreating the task sequence and it still wont show up in the deployment wizard.
↧
Windows 7 32bit Deployment
HI
I am having trouble deploying Windows 7 x86 using MDT 2013 Litetouch deployment. My 64 bit image deploys fine but the 32 bit stops at step 53 of 89. The client machine at step 53 is at the logon screen and if i try logging in it says the local administrator account is disabled. I have enabled monitoring on the deployments share as this is where i noticed the deployment is stuck at step 53.
Is there a way to find out what step 53 is doing?
I set the local admin password during the task sequence so am unsure as to why it wont accept the details.
Thanks
Shane
↧