Hello All,
I currently deploy Win 7 with the use of Lite Touch MDT via USB flash drive. Is there a way to integrate this process with a drive duplicator Omiclone Xi? It currently takes one hour to complete one laptop via a flash drive with the Lite Touch install. We
operate in the Public Safety area where time savings is a concern.
Thanks
We have a highly segmented and geographically diverse network which makes a centralized deployment server not feasible. So, we deploy Litetouch images via USB flash drives. We create a C drive for the OS, a D drive for the data drive and the E drive is generally the CD/DVD drive. The deploy drive winds up being F or higher. This has worked fine until Server 2012 R2/MDT 2013. Now, during the deployment, the USB drive is taking the drive letter of D which causes apps to be installed onto it instead of the data drive. I have tried talking people here into moving to a single C drive deployment which would greatly simplify the build and get around this problem but that is not a desired option. I am not currently using custom WIMs but am not against it if it will solve this problem. We are deploying onto Dell PE-RX20 series servers.
VMs, using the same build do not experience the problem. The deploy drive comes up as F and everything installs as it should. My thoughts there are that the image is mounted as an ISO and the OS cannot write to it so it treats it differently but the physical servers see it as a hard drive and install apps to it.
Any assistance would be appreciated.
I have an application defined in MDT along with its respective files. One of these files is an install and needs to be run locally. How do I copy this file locally then have it run? I've used a fair amount of batch scripts so I opted for that, but every batch script I get (even empty ones or one with just an exit) returns code 1. If I enter in cmd /c directly in the command line with the commands separated by && it would not work either.
I DO not want to hardcode any IP into this which is why this is so hard. Is there no way to do this easily without a full \\IPADDY\Share?
Hello-
In short here's what I need (want) to do... I want to copy 3-4 applications folders from MDT deployment share to the target PC and run install locally. The problem for one is that the install breaks the connection to MDT share thus causing the install to fail. [Cisco VPN Client]. One other app is install using a .cmd command with special internal switches and won't install either.
Thx J-Woo
Hey Guys,
I can't seem to get USMT to kick off right in my task sequence. This is the "Standard Client Task Sequence". I want it to migrate files from Windows 7, reload the computer with a fresh copy of Windows 7, and reapply the migration files.
Here is my customsettings.ini:
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac /lae
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipDeploymentType=YES
DeploymentType=REPLACE
SkipDomainMembership=YES
JoinDomain=xx.xx.xx
DomainAdmin=usernamexx
DomainAdminDomain=xx
DomainAdminPassword=passwordxx
MachineObjectOU=OU=Computers,OU=xx,OU=xx,DC=xx,DC=xx,DC=xx
SkipUserData=YES
UserDataLocation=AUTO
UDShare=\\serverxx\DeploymentDump
UDDir=%ComputerName%
SkipComputerBackup=YES
SkipTaskSequence=YES
TaskSequenceID=2001
SkipComputerName=YES
OSDComputerName=%ComputerName%
SkipLocaleSelection=YES
UILanguage=en-US
UserLocale=en-US
KeyboardLocale=0409:00000409
SkipTimeZone=YES
TimeZoneName=Central Standard Time
SkipApplications=YES
UserID=Administrator
UserDomain=xx
UserPassword=passwordxx
SkipBitLocker=YES
SkipSummary=YES
Here is my Bootstrap.ini:
[Settings]Any ideas? Everything else is working perfectly, except for the fact it isn't migrating any files.
I tell it to Network Boot, and it starts kicking off. But once I get into Windows, no new files.I'm trying to replicate some scripts in the \Scripts folder from a Server 2008 R2 machine running MDT 2012 (update nothing) at our main office out to other servers running the same version of Windows and MDT at our remote sites. I've found that after doing this and opening the task sequence using this new script at the remote site I get the "This task sequence contains one or more errors..." message. The wim file has been wiped out from the "Install Operating System" step. The first time I saw this I fixed it thinking it was a one time glitch. Before I replicated to the second remote site I first opened the ts to make sure the wim file was set, then I closed the MDT console, replicated, opened the ts, same thing, the wim file was removed. Even if I fix it the next replication once again removes the wim. I've also tried uninstalling / reinstalling the MDT console on the source server at our main office, same thing. Looking at the actual ts.xml for the task sequence at the remote site I can see that the wim file is set, why is the GUI not picking it up?
Ideas?
Some back story that may be related: the local primary server that I would normally use to replicate out DS content was updated to 2012 Update 1 by a coworker a while back, but not the other local secondary server and not the remote sites. When I attempted to use my usual replication server yesterday to replicate content I got an error about the versions being different. Fine, I copied the new scripts to the scripts folder, made the ts changes manually, and setup the remote sites as linked deployment shares on my secondary server, and decided I'd just use that for replication. Now I'm thinking maybe something got scrambled when I attemtpted to replicate a 2012 Update 1 DS to 2012 Update nothing.
Hello.
I am having difficulty deploying a custom Windows 7 x64 Enterprise image for a client. The process fails at the "Install Operating System" step. Here is there error page I get during the process:
Here is the process I went through to create this image:
1. Installed Windows 7 64bit Enterprise on a physical reference PC (Dell OptiPlex Desktop). Installed some company-specific apps. Installed IE9. Set some local policies. Did not run Windows Update. Captured. Later, I realized I needed to install Windows KMDF 1.11 so I started the reference machine back up, installed KMDF 1.11, and then sysprepped and re-captured.
2. Created a Deployment Share on a non-domain-joined workstation at path of C:\DeploymentShare$. Left most things default except set it to ask for admin password.
3. Added Windows Intune to applications list with command line "quiet" switch.
4. Created new Operating Systems entry. Chose custom image file, important custom WIM, chose setup files are not needed, chose destination directory name "Win7Ent".
5. Added drivers. I created two driver folders, one for "WinPE 5.0" and one for "Windows 7 x64 Ent". Imported Windows PE 5.0 driver cab from Dell into PE folder (it completed with 6 warnings, all similar to"Warning: Driver.... does not appear to support platform x86 as indicated. Overriding the indicated platform.") Imported Windows 7 Dell driver cabs for E5440, E7240, M4800 (completed with 75 warnings, same as with PE drivers). Created selected profile for WinPE5.0 and selected the PE folder, including all x86 and x64 drivers - then, went into Deployment Share properties, in Windows PE, under Drivers, set the driver selection profile to this (also set scratch space for PE to 256mb).
6. Created task sequence: standard task sequence, chose "Do not specify product key" and "Do not specify local admin password".
8. Updated deployment share. Completely regenerated boot images.
9. Created and updated media.
10. Moved contents of "Content" folder in media folder onto a flash drive. Put the drive into a Dell E5440 and attempted to run the Deploy task sequence. It seemed to start working. It passed the format and driver injection steps and then not long after I get the errors.
I have done and redone this over and over again and scoured the web for any ideas and I can find nothing that might be breaking this process. Any ideas you all might have would be VERY appreciated. Thank you.
Hello all,
I ran into a situation that BitLocker PIN/BitLocker Password Screen has wrong Computer Name as part of the Drive Label.
It turned out that computer name was wrong while the technician is deploying W7 via MDT (and BitLocker Encryption is done as part of it) but corrected it after the fact. As a results:
Even though the computer name is properly named OK (ASSETXYZ), BitLocker PIN and BItLocker Recovery Password screen shows MININT-xxxxxxxx (or whatever previous name it was):
We confirmed that fully decrypting (40 mins) + and re-encrypting (40 mins) resolve the issue but we don't want to spend 80 mins just to fix this issue (obviously)...
Is there any way to change this via Commandline, etc.?
Thanks,
YPae
Hello. My environment is SCCM 2012 SP1 with MDT 2012 Update 1 integrated. We will be moving to R2 and MDT 2013 in the near future. I have a question about the summary page. I have built several custom pages for my deployments. I have noticed that one of the pages display it's selected value on the summary screen but the other two do not. For example, I have a custom page that asked the builder to pick an application suite. When the builder gets to the summary page, the friendly display name for the application suite and their selected value is present. I have another page that asks for the location of the machine. When the builder gets to the summary pages, neither the friendly display name or selected value are present. Both custom pages, use combo boxes with friendly display names configured in the settings of each page.
Everything else works well otherwise but I would like for the builders to see the values they picked on the summary page. Is there something I am missing on my custom pages that is preventing it from appearing in the summary page?
Thank you for the assistance.
Using MDT 2012 SP1, I capture a custom Windows Image using the stock sysprep and capture Task Sequence. When I deploy the image using either a custom or stock deployment TS, after it boots into Windows, it says that the task sequence cannot be found on C:\minnt and then D:\minint. To fix the problem, I have to mount the captured wim and remove the following directories:
MININT
Sources
_SMSTask Sequence
Shouldn't these folders be removed at some point to make way for the deployment files? Does this have to do with partition modification?
Orange County District Attorney
Orange County District Attorney
I have a task sequence that builds my reference image completely automatically and capures the wim file to network share with hard coded name. I would like to use my naming standard like W7-ENT-x64-REF and append year & date to this filename automatically.
I found this example from google but this gives me error
BackupFile=%TaskSequenceID%_#month(date) & “-” & day(date)& “-” & year(date)#.wim
How I can do this?
Hi Everyone,
This is a tricky one, I've been scratching my head for a few days now. I have a MDT deployment share, which lives on a server, for argument sake, lets call it: MDT-01. Via the Servers MDT Workbench, I can connect to the deployment share just fine, from any PC, other than my main PC (which is running Windows 8.1), I can connect to the deployment share just fine. If I load the MDT Workbench on my main PC, it just has a deployment share folder with a red cross on it. If I attempt to remove it, it crashes the MMC, if I try and open the same deployment share it crashes the MMC. If I give the Deployment Share a different share name, it errors and says I can't use an existing deployment share folder.
I used to be able to connect to the share just fine, but since the last couple of days I've not been able to connect.
Further investigation with PowerShell reveals that the console thinks it has a persistent drive, DS001, but the path is blank, as in ''.
Restore-MDTPersistentDrive -verbose
VERBOSE: Restoring drive 'DS001' with path ''
WARNING: Unable to restore drive DS001.
If I try to remove the Persistent drive, it errors, and if I try to add any new drive to either the same deployment share, or an alternative, it fails.
I can use the New-PSDrive and Remove-PSDrive Powershell commands to create/remove a replicated drive, but that doesn't actually change the Path value in the Get/Restore-MDTPersistantDrive, as they seem to be separate, even though I think they should be linked.
The Internet has been no help, so I'm asking the Microsoft crew to be helpful, and not just do the usual "This is posted in the wrong place, this question will now be closed... etc, etc!" This is an MDT question, not a Powershell question, I just need anyone who has indepth MDT knowledge to look at this.
To make clear, this is not a question about a client connecting to the deployment share, that all works fine, and I can update the deployment share fine from any other workbench.
I cannot connect to my deployment share, from my local MMC MDT workbench, as it thinks it already has one, but with a blank path. I've uninstalled, and reinstalled both the MDT, and ADK components on my Local PC, but I still cannot connect to the Share.
My question is this: The files/registry that stores this DS001 path setting is clearly local to my PC, but where is it, I've search the reg, and I've check files, but to no avail, I'm likely to rebuild my PC because of this, but I'd rather not if I can help it.
Any Ideas people?
P.s. Sorry if this post seems rude, I do appreciate the help, I just don't have time for being messed about, as we're migrating our XP system to 7, and with less than 60 days remaininf, I could do without this... Thanks for understanding. :D
Orange County District Attorney
I use MDT 2012 to build, capture and deploy Win7 x64. I have used selection profiles for my pc-models and drivers. On HP 8440p everything works fine but when im trying to inject drivers for HP Z400 with a Barco display card dhe drivers wont get injected, or not installd. I have imported the right drivers to Out-of-Box drivers and can see the there. The inject drivers step for Z400 in my TS runs and seems to be working but when the OS is installed the displaydriver is Standard VGA-driver.
When I then test to install the driver manualy, via the Device Manager and browsing for the driver on the deployment share, the driver gets installed and everything works great.
Have tried both "Install only matching drivers..." and Install all drivers" in the TS step!
How can I get the driver to install in TS with th Inject Drivers step?
TWP
Hi all MDT guru,
simply question. We are using all driver on one place in Out-of-Box driver, because we have only two version of desktop based on intel. But now, we have another brand desktop and I would like use inject direct driver. This is still not a problem, not counting
the bad drivers that must be installed. Here I still do not know how I to recognize.
I would like ask for another question. If you import driver, do you import only single one correct driver or all pack from brand CD or all in one driver cab ?
Looks like stupid question but it's easy to put CD with all driver and import them to right folder. Problem was, that wizard import drivers, that I never need. If I download driver from web it's same problem, one pack for dozens of sound cards, so than I
have in "out of box drivers" hundreds of unwanted drivers.
If you preferring only one correct driver (which I think) to injecting correct driver do you use any tool to find the right one ? Or script to find the correct driver name. How to find and choose the right one ? Or you use the detail after rimport driver
and check PnP ?
Thank for help and sorry for my English an maybe stupid question.
Hi everyone,
In our environment we use MDT 2010 and WDS version 1.0 on Server 2008 standard SP2.
This week, we have received a new model workstation, HP EliteDesk G1 800.
I download the NIC drivers off the support web page of HP, The driver itself is: Intel (R) Eternet Connnction I217-LM.
I just want add the driver to a boot image in Windows Deployment Services, But - Because we have WDS 2008 standard we can't
add the driver via WDS ( I did read that it is only there on Server 2008 R2. the management console doesn't show a "Drivers" node under the WDS server 2008 standard.).
So, How can I add the NIC drivers to our windows7 image in the WDS 2008 standard ???
thanks
Hello! I seem to keep receiving these errors in my deployment on all my task sequences all of a sudden. Can someone help interpret these errors??
Thanks!
I changed my setting to 500% under the "make text and other items larger or smaller" in the "resolution" screen, now the screen is too big to allow me to go back in and change it to the normal setting. How can I get this done. I already have tried the "enable low resolution video mode" but that does not work for this. Help is needed.
thank you.