Jump to content


Search the Community

Showing results for tags 'mdt'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 100 results

  1. Hi All, I was wondering what the best approach would be to assign multiple machines each with their own unique computer name during my deployment. I have been given the responsibility to deploy about 100 computers in an environment and needed to assign different computer names to each machine. Currently I have a setup using MDT for the actual deployment and WDS that is used for the PXE boot. Is there a way (preferable without using a PowerShell script) that I can deploy these machines? The reason I say preferably without PowerShell script is because I'm a rookie with scripting. If there is any other way to do this, please let me know! Thanks for any help you guys can provide! -Mehrdad
  2. hi guys i'm doing a lab from the book System Center 2012 Configuration Manager: Mastering the Fundamentals by Kent Agerlund, and in it, there is a refresh to win 7 from xp lab using mdt integraated with config manger. I'm following the instructions exactly, but everytime i run the task sequence to install the os, im getting an error even before getting to boot to winpe. Everything seems to be running fine, but then the task sequence errors out with this message Task Sequence: Windows 7 ent x64 has failed with the error code (0x0000264C). For more information, contact your system administrator or helpdesk operator. Then in Software Center I see this error Error: 0x4005(16389) I examined the smsts log and only see this error Error getting system isolation info. Code 8027000C Remediation failed. Code 8027000C Remediation failed with error code 8027000c researching the error codes i dont find a lot of information, suggesting maybe it could be a driver issue. i didn't add any drivers to my boot image but I was able to get into winpe before and it was the same task sequence using the same boot image so i'm unsure if thats the reason for the error im using vmware workstation 9 and sccm 2012 sp 1. thanks to anybody that can help EDIT* Ok i resolved the above issue (memory wasn't set correctly) but now im booting in win pe and getting "unable to read task sequence configuration disk" and navigating to smsts log i see error failed to find the configuration path error 80070003 One person resolved it by updating the bios but im not sure if that is the issue
  3. Here i'm again. I'm getting frustrated Situation, i'm about to install MDT 2012 to upgrade our MDT 2010. No the 'problem' is that some off the customsettings features like computername are changed in osdcomputername, some things are deprecated some are new features. So far so good. I have installed the deploymentshare on to DFS and now i like to customize my settings into SQL, based on locations and gateway. Here is my customsettings.ini [settings] Priority=Locations, Default Properties=MyCustomProperty [Default] EventService=http://server:9800 [Locations] SQLServer=server.domain DBID=user DBPwd=***** Instance=MSSQLSERVER Port=1433 Database=DEV_MDT Netlib=DBNMPNTW Table=Locations Parameters=DefaultGateway When i check by following url the connection to my DB everything is going well http://deployment.xtremeconsulting.com/tag/ztigather/ This is my ztigather.log, i have filtered out where the sql section Added new custom property MYCUSTOMPROPERTY Using from [settings]: Rule Priority = LOCATIONS, DEFAULT ------ Processing the [LOCATIONS] section ------ Determining the INI file to use. Using DEFAULT VALUE: Ini file = \\server\CustomSettings.ini Finished determining the INI file to use. Using specified INI file = \\%server%\CustomSettings.ini CHECKING the [LOCATIONS] section Using from [LOCATIONS]: SQLServer = server.domain Using from [LOCATIONS]: Instance = MSSQLSERVER Using from [LOCATIONS]: Port = 1433 Using from [LOCATIONS]: Database = DEV_MDT Using from [LOCATIONS]: Netlib = DBMSSOCN Using from [LOCATIONS]: Table = Locations StoredProcedure key not defined in the section [LOCATIONS] Using from [LOCATIONS]: DBID = user Using from [LOCATIONS]: DBPwd = ******** SQLShare key not defined in the section [LOCATIONS] ParameterCondition key not defined in the section [LOCATIONS] Default ParameterCondition 'AND' will be used for building queries with multiple parameters. OPENING STANDARD SECURITY SQL CONNECTION to server server.domain using login user. <Message containing password has been suppressed> Successfully opened connection to database. About to issue SQL statement: SELECT * FROM Locations WHERE DEFAULTGATEWAY IN ('10.4.176.1','fe80::be16:65ff:fe87:d701') Successfully queried the database. Records returned from SQL = 1 Property LOCATION001 is now = Test Added LOCATION value from SQL: LOCATION = Test ------ Processing the [DEFAULT] section ------ Property SLSHAREDYNAMICLOGGING is now = \\server\SLShareDynamicLogging\%OSDComputername% Using from [DEFAULT]: SLSHAREDYNAMICLOGGING = \\server\SLShareDynamicLogging\%OSDComputername% Property EVENTSERVICE is now = http://server:9800 Using from [DEFAULT]: EVENTSERVICE = http://server:9800 ------ Done processing \\server\CustomSettings.ini ------ Correct me if i'm wrong but the sql connection is OK, the select statement results OK but he's not processing the rule from Test that are set in the DB. Can somebody please help me !
  4. My environment Configuration Manager 2012 SP1 Integrated MDT 2012 U1 1 Site Server with all roles (DP, SUP, MP, etc) Reference Windows 7 X64 Pro image Deployed using MDT integrated task sequence in ConfigMgr 2012 SP1 The reference image did use C: for the OSDisk I'm attempting to deploy my reference image to virtual machines using VMware. The image does get pushed down however it installs the OS to D: DiskPart on the deployed image shows the following: Volume 0 E: DVD-ROM Volume 1 BDEDrive Volume 2 D: OSDisk I have edited my task sequence to OSDPreserveDriveLetter=True BDEDrive is checked "do not assign a drive letter to this partition" under PreInstall -> Format Disk Here is my customsettings.ini [settings] Priority=Default Properties= OSDMigrateConfigFiles,OSDMigrateMode [Default] SLShare=\\SERVER\logs$ DoCapture=NO ComputerBackupLocation=NONE BDEInstallSuppress=YES MachineObjectOU=OU=Workstations,DC=DOMAIN,DC=NET OSDMigrateMode=Advanced OSDMigrateAdditionalCaptureOptions=/ue:*\* /ui:DOMAIN\* OSDMigrateConfigFiles=Miguser.xml,Migapp.xml
  5. We began creating our Win 7 image in MDT 2012, but the image was created with MDT on a physical Win7 x64 machine in my cubicle. The image and deployment share look good, LTI task sequence, drivers, base OS and scripts are all set - it's ready to go! But we want to deploy it with SCCM. We have an SCCM 2012 SP1 Hierarchy w/CAS environment setup. I searched around a lot, looked through guides, but haven't found a solution for this scenario yet: Q: What would I need to do to take my existing MDT deployment share from this physical PC, and move it to SCCM? So that there would be no dependency on the original physical PC. I assume I'd need to install MDT on the SCCM CAS and copy the entire DS to it? I'm a bit lost at where to start from this point, and would appreciate any input. Thanks!
  6. I have an inherited environment and just trying to understand the PXE process Currently I: In SCCM Add computer manually in SCCM Add computer to collection to boot and reimage computer with XP image Go to computer, reboot and press f12 to PXE boot and f12 to start imaging The imaging actually goes to a MDT image screen (to select the image from MDT to use) My assumption ....is: The PXE server checks to see if there is a SCCM advertisement for the computers MAC address, if there isn't it passes it on to MDT to give the computer an image. A few hours later if you boot the PC and f12 the SCCM image is sucessfully loaded. I am assuming that it takes a few hours for "all" of SCCM to know it exisits? Is this "normal" behaviour for MDT to be the fallback image option? cheers Lesta
  7. I have SCCM 2012 SP1 setup with MDT integration. I have setup the Software Base Variable to Coalescedapps in the UDI properties. I setup the TS to install as shown below, but it just blows by the stage. I took the default Install Applications sequence from the MDT wizard and added a Run Command Line that exports the variables to text file. CONVERT LIST TO TWO DIGITS: "cscript.exe "%deployroot%\scripts\ZTICoalesce.wsf" /CoalescePattern:Applications /CoalesceTarget:CoalescedApps /CoalesceDigits:2" RUN COMMAND LINE: "script.exe %deployroot%\scripts\CUSTOM_SCCMVariables.vbs" INSTALL APPS: (SCREENSHOT BELOW) If I go into the Variable text file, I have this output: If I look in the OSDSetupWizard.log I see Problem is I dont see anything in the smsts.log and when I get to the Deployment Complete screen, it shows the apps with ! and Install State unknown, similar to http://social.technet.microsoft.com/Forums/en-US/mdt/thread/68f67f55-1d55-469e-9fb8-225030f42ff2 EXCEPT my applications dont install. For some reason, the OSD App Name keeps showing up with the extra 0 in there as well. OSD App Name: COALESCEDAPPS001 Im guessing it's looking for COALESCEDAPPS001 instead of COALESCEDAPPS01. I'm not sure why it's picking up the variable with the extra 0 in front. Any suggestions would be appreciated. Thanks David
  8. I have been working for a company for a while almost a year and we have been using Ghost to image the machines. This has been very good and has worked very reliably for the company for many years. However, recently I have been encountering a lot of issues due to drivers, especially since we now have a lot of new Lenovo Laptops and various other models besides Dell now. Basically we have 1 Master Image with every driver on it for all the different models we have about 10 models or so. I really could use the help with this, I have been very quiet but I have read a lot of posts, forums, articles and watched countless videos just not sure what I actually need and if it is even possible. What I want (future) Migrate from Ghost to MDT easily without loosing all the work that was done to make the current images. MDT because managing drivers appears easier and more precise; so the correct model and driver should always be used and installed. PXE Boot / Light Touch or Zero Touch Windows 7 and Windows 8 Imaging Only no XP The Current Setup. Dedicated Local Gigabit Network for Ghosting which includes Server 2003 running DHCP, DNS and Ghost Our Images are stock full of customization and changes. I do not want to re-create / re-install all these applications again. Problems: Drivers get installed on computer that it can't use or doesn't belong to No DOS drivers for lenovo laptops have to remove drive and image manually. Since our images are very customized already with lots of oracle configuration changes that have been made specifically for our environment how can I preserve this image and migrate it to MDT without having to re-do all this customization? Would this even be possible? I have the following software available to me: -Windows Server 2008R2 and Server 2012 -SCCM 2012 don't really want to use it... little big I think! -Windows 7
  9. I had a request from a previous post to share how we are changing the computer description during OSD. We currently use this to have our techs enter in the location of the computer to help with automating our inventory. Also, if anyone has a better way of doing this please feel free to contribute. Also, in our environment the description does not filter back to AD it only remains local to the machine but YMMV as I haven't looked too far into that. The description still filters back in through a custom report so it achieves everything that we need it to. 1. Create a computer description TS variable 2. Include the following script as part of one your packages and execute it sometime before your OS install (we include all of our scripts in the MDT Toolkit package) TSComputerDescPrompt.vbs Dim oTaskSequence, strComputerDesc Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' The wscript.echo commands are logged in SMSTS.log for troubleshooting. ' They are not displayed to the end user. sComputerDesc = InputBox ("Enter desired computer description." &VbCrLf & VbCrLf & "X Domain - Computer location example: BUILDING ROOM #" &VbCrLf &VbCrLf & "Domain - Tag Number example: 10-0454 or 106183","Computer Description",,,30) oTaskSequence("OSDComputerDesc") = sComputerDesc wscript.echo "Set Task Sequence variable OSDComputerDesc to: " & strComputerDesc 3. Execute this final script with another task sometime after the OS install, we do it right after. TSComputerDesc.vbs Dim objShell Dim oTaskSequence, strComputerDesc Set objShell = WScript.CreateObject ("WScript.shell") Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' The wscript.echo commands are logged in SMSTS.log for troubleshooting. ' They are not displayed to the end user. strComputerDesc = oTaskSequence("OSDComputerDesc") objShell.run "reg add HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters /v srvcomment /d " & strComputerDesc & " /f" wscript.echo "Computer Description changed to: " & strComputerDesc
  10. I work for a large company. We'll deploy Win7 to hundreds of computers with MDT medias (install from USB because of network portion was not ready). We plan to do the subsequent installations via SCCM. But I'd like to do lite touch installation with SCCM 2007 R3; while installing, setup should ask for computer name, where it should reside in (I'm using domainou.xml file with MDT) and time zone. Is this possible?
  11. Hello All, We are performing LTI with the UDI module. When administrator enters the intended name of the computer we need to get this name (presumably OSDComputerName task sequence variable) and add some text to it. We already got the concatenating portion of the script, but need help with the first part and the third parts. So, basically we need to perform the following sub-tasks: Get the task sequence variable with the intended computer name which was entered by the administrator. Verify/modify it (this portion we already implemented) Set the task sequence variable using the modified computer name. Would you be so kind to advise on the following questions: Should we use the OSDComputerName task sequence variable or any other else? What the code in the PowerShell should be in order to get the input from the administrator and set the new computer name? What is the proper location of this task should be in the task sequence? We prefer to get it before the OS is installed, but would highly appreciate if you provide is with the location. Also, we received the following error: PS C:\Windows\system32> $tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment New-Object : Cannot load COM type Microsoft.SMS.TSEnvironment. At line:1 char:20 + $tsenv = New-Object <<<< -COMObject Microsoft.SMS.TSEnvironment + CategoryInfo : InvalidType: ( [New-Object], PSArgumentException + FullyQualifiedErrorId : CannotLoadComObjectType,Microsoft.PowerShell.Commands.NewObjectCommand Thank you very much for your time and help!
  12. We want to set a password (using UDI) before a user is allowed to select a TS. For example, we would like to advertise a ts to software center. If users select it, without a password (before booting into winpe) they will not be able to proceed. Is this possible?
  13. Hi all, I'm engineering an MDT2012 Task Sequence to migrate users from XP to 7. First I use Hard link migration, then I reboot to capture a .WIM backup using ZTIBackup data in WinPE, followd by the Windows installation. In Win7 to Win7, I seem to never have any issue, deployments complete without any problems. However in Xp to 7, using PC's with actual user data, I am experiencing a very high, nearly 85% failure on the ImageX step. I get errors in ZTIBackup.log and in BDD.log that the system cannot find the file specified. Fearing disk errors, I've added a Disk Cleanup pass that runs: cmd.exe /c reg import "%deployroot%\Scripts\Custom\cleanmgr.reg" cleanmgr /sagerun:777 Which I've confirmed works for those purposes. I've also added a Check Disk /f /x command in front of the Wim backup step in WinPE, which I've also confirmed works as expected. So...I'm not sure why in the world this keeps happening. Every PC seems to do this on a different file, which always is located in the User's profile somewhere, normally the desktop. I've done numerous google searches but it also seems that no one ever gets to the bottom of this. The USMT hard link works as expected and the user's lose no data. Still, this is very strange behavior. imageX errors.txt
  14. Ok, currently, I have our Deployment Share on our regular deployment server (MDT001) and I've created a Linked Deployment Share on a network location in our Northern branch. Their x86 Linked Deployment Share boot image is working and all the information seems to be pulling from our database (MDTDB) and populating the information. However, I'm trying to set them up with a x64 boot image for doing our Engineering Workstations, but it just sits and asks for a role. It seems to be seeing it enough to know which roles are available, but it's not seeing my database that tells it which role and which applications to pull from. I thought I've copied all the bootstrap.ini settings from the x86 image that does work, but it's still not working. Can anyone tell me what I might be missing? On a bigger picture, am I using the Linked Deployment Share as it was intended? Should I create a database and store it locally on the remote server in our Northern branch, and if so, how do I do that?
  15. Hi, Suddenly I'm unable to open/edit an existing Task Sequence in MDT 2010 Update 1. I click properties on the Task Sequence then click the "Task Sequence" or "OS Info" tab then get an "MMC has detected an error in a snap-in and will unload it". I can click those two tabs on the properties of other Task Sequences and not get the MMC message. Any advice would be greatly appreciated. Thanks!
  16. Hello, First I'd like to say thanks for this site. It has been incredibly helpful and has been a blessing. I'm running MDT 2010 update 1 and I'm having an intermittent but relatively consistent issue when trying to deploy Office 2010 and 2007. I have a base Windows 7 image deployed and an install applicaiton task sequence for the Office product. Sometimes the Office installation fails (other applications install fine) and I get an unexpected return code 20 on the LTI summary page. The application install log file shows the following: LIS failed to cache download "{90140000-0011-0000-1000-0000000FF1CE}-C" resource "ProPsWW.cab". Cache Error 0x80070040 Source Resolution aborted Error: LIS: Failed to cache download "{90140000-0011-0000-1000-0000000FF1CE}-C" resource "ProPsWW.cab". Type: 20::FileNotFound. What I see in the Window7 app log is that Office get's installed...then errors, then uninstalls itself. In the deployment share, ProPsWW.cab is in the appropriate spot with the appropriate permissions. Again, sometimes the install works, sometimes it doesn't. I created an Application Install only Task Sequence...and with this...sometimes it works, sometimes it errors out with the same reason as mentioned above. I believe when MDT/LTI goes through the deployment process it copies the applications files over to the MSOcache. Are some files not properly copied over? Do I even have the correct understanding? Any help would be very appreciated. Michael.
  17. We recently upgraded our MDT package and since the change the MDT TS comes back with Unable to access the domain when entering in Domain Join Credentials. What logs would help troubleshoot this problem and where can they be found?
  18. Hi, I've created a UDI Task sequence with MDT 2012 and SCCM 2012, everything works fine, except i want to validate the computer name the will be inputed in once of the forms against the AD web service. expect i don't undestand how to do so, i've install the web service and it works fine, but i don't understand what i need to edit in order to have this validation in one of the pages in UDI wizard. help would be much appreciated, as i want to use this web service for other things as well in my UDI. Thank you in advance.
  19. I've tried everything I can think of to get this working. After doing quite a bit of research online it looks like everyone has their own way of doing the entire process of customizing, capturing, and deploying Windows 7. As it stands, I've integrated MDT 2012 with my current SCCM 2012 (using this guide) and have tried a couple of the build, capture deploy methods I've found online but cannot for the life of me get the SCCM 2012 / MDT 2012 User Driven Installation to work. I can however get the SCCM 2012 Zero Touch Installation to work without a hitch using the same wim so I'm sure it has something to do with the UDI TS. Basically, I've built a custom Windows 7 Enterprise SP1 x86 reference machine with all applications and customization needed and then captured the image using SCCM 2012 Capture Media (using this guide). It creates a wim file with two images, 1-1 is the 100 MB System Partition, 2-2 is the Windows Install. So in any of my deployment task sequences I tell it to lay down the 2-2 image. Also the Network Access Account has been created and have verified that it has Full Permission to the content locations. Next I followed guides 16, 17 and 18to integrate MDT 2012 with SCCM 2012 and to deploy a UDI. At first I found that it was creating two partitions a (C:) BDEDrive and (D:) OSDrive and was trying to apply the image to the D: drive. So I added DoNotCreateExtraPartition=YES to the CustomSettings.ini file, removed the BDEDrive 512 MB volume from the Format and Partition Disk section of the task sequence and set the OSDisk (Primary) as the boot partition. Now it still fails, any help with this would be greatly appreciated. I've attached the most recent SMTS.log below. smsts.log
  20. If anyone is interested, I have just produced (today) a solution to use WDS as a PXE boot point, to Boot PE and then automatically run a batch to image a PC using imagex to a nominated (in batch) file share, we've had a lot of leavers lately and I needed a quick way of backing up a lot of machines. If anyone is interested in this, i'll document it up. Aaron
  21. Hi there. Looking for some advise regarding Windows 7 deployment & PXE Booting. Background - we are using sccm 2007 & mdt 2010, and are currently in the middle of a project to migrate our OS to Windows 7. We have a server (sccmbr01) which has been added as an sccm site-system, which contains the OS images & runs the WDS role; within sccm this is configured as a PXE Service Point. The server had been happily sitting on its own subnet, happily deploying OS images, and providing both DHCP & PXE services. However, Management have now, in their wisdom, decided to move this server onto the main ip subnet where our general server population are located. This still worked ok, as long as sccmbr01 was providing dhcp service, with the scope set to a single subnet unused by any other devices. Our problem at the moment is that we are looking to extend the OSD service - including PXE boot - throughout the organisation, so that we can perform "in situ" rebuilds & refreshes, etc. (estate - approx 5000 pcs, approx 200 subnets, many geographic locations etc). The Comms team want to configure this so that DHCP for PXE boot/OSD is provided by our regular domain DHCP servers - their argument is that if we extend the DHCP scopes provided by sccmbr01, the addresses will be used up by the general PC population, i.e., this will become just another regular DHCP server on the WAN. Comms have configured "ip helper" on the routers, etc; however, after several attempts, using different permutations, we have not been able to successfulyl PXE boot client. When sccmbr01 had dhcp active, the files/paths displayed after F12 network boot were as follows, in order of appearance \smsboot\x64\pxeboot.com \smsboot\boot.sdi \smsimages\smspkg\pr10022b\winpe.pr10022b.wim We have tried to configure the DHCP servers to point to the above files, without success. \smsboot\x64\pxeboot.com - launches "Windows Boot Manager" console, with the following error - "file - \bbot\bcd status - 0xc000000f info - an error occurred while attempting to read the boot configuration data" \smsboot\boot.sdi - displays error "too big to fit in memory" \smsimages\smspkg\pr10022b\winpe.pr10022b.wim - displays TFTP error When we leave DHCP unconfigured, using only IP Helper (this seems to be the recommended method), an error 53 (boot file not found) is displayed. Do you have any suggestions what we could try next, or something we may be missing? I found this thread which seems to be quite similar: http://www.windows-noob.com/forums/index.php?/topic/890-bootbcd-error/ Any suggestions would be gratefully sppreciated. Regards Stan
  22. I'm using MDT Task Sequences with SCCM and am trying to get a proper Computer Description set. It was easy to do with OSDComputerName and check if a computer was already named properly in AD for whether or not a popup would ask for a new name. Now I've tried using the same method for setting the computer description. I've made sure that my Discovery settings includes the Description property, so I can see the AD Description in my Devices properties. The problem is how to set a task sequence variable to use the variable assigned to my device. I thought setting a variable: OSDComputerDesc with a value: %Description% would do it, but that was a bad guess. How do I bring in the Device Property Value and give it to my new TS Variable?
  23. Hi folks, This is my first post so please bear with me. This is my environment. 1 x Forest Root DC with Win2008 R2 SP1 1 x MDT Server with MDT 2010 and WDS running Win2008 R2 SP1 1 x Technician laptop with Windows 7 x86 SP1 and WAIK PE3.1 I am currently deploying Windows 7 x86 to another laptop. I start the PXE boot and the laptop builds into Windows 7 and completes. I am not deploying any packages. This at the moment is a very basic answer file with a few skips such as the welcome screen etc. This all works. Great!... However the problem occurs when I want to change my answer file and try rebuilding the laptop again. It PXE boots into MDT and then just reboots back into Windows without re deploying the image. However if I try building a new stations that hasn't already had an MDT deployment it builds no problem. Also even if I don't change my answer file it does exactly the same. Does anyone have an answer to this? I'm pulling my hair out. :angry:
  24. Hello! Just started with deployment of applications and operativsystems and MDT seems to be a important part of that so i would like to learn a little more about it. I cant realy find any good documentation of MDT, what the scripts does and how i can use it. Where should i start? // Barty
  25. Hi guys, I stumbled across this site through google and I think this might be the best place for me to ask some broad (as well as some very pointed) questions about the whole thing. First off, this acronym soup is killing me. I've got a pretty healthy list of things I need to remember now. With that being said, here is what I currently am doing to deploy Windows 7 to our computers (Mostly Dells): 1. Use MDT to add applications, out-of-box drivers (organized into Operating system, then machine model), and a custom task sequence to rename the primary partition "Local Disk". 2. Add the Lite Touch iso created by MDT into WDS. Do a normal WDS deployment via PXE So my questions really are these: 1. Is this a reasonable way to do it? 2. How can I improve it to make it as automated as possible? 3. Where does WSIM come into play? I would love to be able to define some settings, but also they very from computer to computer slightly. Can I create multiple autounattend.xml files that all use the same install.wim file? 4. How can I set the computer name automatically to be the dell service tag during install instead of declaring it during the Deployment Wizard? 5. How do I update my install.wim file with new Windows Updates offline (by NOT installing Windows onto a reference machine and capturing a new wim file)? 6. In a general sense, can I continue to do most things in MDT and then use WDS to actually push the OS out? Is that the standard method? Thanks! Brian
×
×
  • Create New...