I know this may seem like a trivial thing, but for whatever reason, the ability to rename linked deployment shares has been removed from MDT 2012. Or am I doing something wrong? In 2010 it used to be a simple right-click and rename. I have 10 sites I manage and it is a hassle when they are all named "LINKEDXXX". Any ideas on how I would be able to manually change the name? Thanks.
Len
I am having a problem getting around the 3 rearm limit when maintaining Win 7 images for patching. When I use a install.wim file from the OS media I get the 3 rearms available as I expected. The issue is that when I apply patches to the image for PCI compliance it goes directly to 1 rearm available. Obviously this is an issue as I need to patch the image every month on patch Tuesday.
I placed an unattend.xml file in the windows\system32\sysprep folder to try and skip rearm. This is not working as I expected.
The unattend looks like this:
<SkipRearm>1</SkipRearm>
What am I doing wrong here?
I would like to always have the rearm count at 3 if possible.
Paul Prindle MCP, A+
Hello,
I am new to this forum and hope you can help me out :)
I created a custom property in my customsettings.ini
This is used in OSDComputername
I tried to set a default value for the custom property but it will not be changed again!
In the given example the value will stay at TTT, any ideas?
The Priority is correct as some other things would have failed otherwise in my real code.
[Settings] Priority=InitDefs,Default Properties=MyCustomProperty [InitDefs] MyCustomProperty=TTT [Default] MyCustomProperty=ZZZ OSInstall=Y
i have just installed a new MDT Server. Im absolutly new to MDT 2012.
I would like to replace our windows 2003 Ris server with a new 2008 R 8 Deployment Server. I have manged to do an installation in to VM. So i think i have Base Knowlegement how it works.
My Problem is, that when i try to start the Light Touch win PE, no matter thru PXE or from CD i´ll get an Error =0x0000260 -> "This os uses the Physical Address Extension feature... "
Im trying to Deploy XP Sp3 on an IBM T43
to me it seems that every client has to be be PAE cappable ? whats with my old Clients that are not cappable of PAE ? Can i Modify the PE so that is does not Use PAE. Or do i have to use an older Version of WAIK / ADK. Currently i have only installed ADK 8.59.25584.
Any help would be greatly appreciated !
Thanks
Hi,
I have a strange problem with the UDI 2012 Wizard. When one of my colleagues create a custom page and I open it I see a completely empty page.
If I run the preview the page show up fine but if I edit, it is all blank besides the correct headline.
As additional info I can say that the page actually works just fine in production. I just cannot see it properly. Tried from different machines and with different profiles :(
Any ideas?
I'm sure I'm missing something but I have installed MDT 2012 Update 1, the latest WAIK with the Supplement, and the only OS in my deployment share is Windows 7 SP1 but for some reason the WinPE image is still 3.0 (confirmed by registry from within the PE image). When creating the boot media and watching the status, it is def pulling the boot.wim from the Win7 SP1 folder is this correct?
I may even be hitting this the wrong way... we recently had a new model desktop arrive with Advanced Format drives in it. After trying to deploy with the current setup I was getting the error "Windows setup could not configure Windows to run on this computers hardware" - after a brief Google it seemed the the AF Drives were to blame and upgrading to WinPE 3.1 would solve the issue!
The spanner is that it is also in RAID 1, though this does not seem to be the problem as the drive is recognised and the copy / installation phase of setup completes fine, only the configuration phase has the problem as above.
So two part question:
1. Is this the correct way to implement WinPE 3.1?
2. Will this solve the AF HDD issues we are having?
Thanks in advance guys!
My Blog: DeployXP [Under Construction]| Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene
I had generated an iso with windows 7 and windows server 2008 R2. i am using a bootable pendrive to install operating system. i need to join domain so i am giving all credentials in tasksequence before starting the deployment. once the OS installation finshes it will run the state restore. at the end i am getting a error msg on Tatoo.
please help me on this error. whether its not getting the DNS server to join the domain ?
kindly please help to resolve this error.
Orange County District Attorney
Hi,
I am trying to create a multicast season but due to the deployment share not being local it fails.
Is there any way to set the local path so it will work.
I mapped a network drive but that didnt help.
We have updated our deployment share from MDT 2010 to 2012 update 1. I have downloaded and installed the new ADK for deploying windows 8. I have tested and successfully deployed both x86 and x64 operating systems after performing the update and install of ADK.
However, (even though the deployment actually works) there is an error message titled "remote connection" with the body "The operating system version is not compatible with this product"
This error occurs when you click on "Run the deployment wizard to deploy an operating system". It seems to only occur in the x64 version of lite touch.
Below is an image of the components that are registered in MDT (unsure if this will help anyone). The question is how can we get rid of this message? :)
<h2>Select Server Configuration:</h2><span style="width:95%;"><table><tr valign=top> <td> <input type=radio name="ServerConfig" id="BASE" checked language=vbscript AccessKey=A
> </td> <td> <Label class="Larger" for="BASE" language=vbscript >Base
Config</Label> </td></tr><tr valign=top> <td> <input type=radio name="ServerConfig" id="SQL" language=vbscript AccessKey=A
> </td> <td> <Label class="Larger" for="SQL" language=vbscript >SQL
Config</Label> </td></tr>Hey guys,
I'm tinkering with MDT 2012 and trying to setup a task sequence to deploy windows 7 and windows 8 to independant VHD's in a dual boot setup. I've seen a little feedback on this forum saying it's not possible. I'm not sure why it would be impossible as the mechanics seem to be (mostly) there. I can create a task sequence that includes two OS and two VHD with different variable names, and point each install to the appropriate VHD via its' variable name.
What is actually stumping me in this is that as part of the deployment wizard it asks me for the computername, which I only enter once. I want to know how I can customize this so that it asks me twice and applies the name to the correct OS?
Thank you,
Ryan
Hello,
I currently have a problem that Windows deployment won't continue automatically when i add reseal | audit to 7. oobesystem in the unattended.xml
i have to manually excecute the ltibootstrap.vbs before i start litetouch.wsf
With windows 7 it was easy enough to get the tasksequence to continue with "cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start" as runsynchronouscommand.
but in windows 8 i get a error that the task sequencer can't be found because the tools folder hasn't been copied over to the MININT folder.
without booting into audit mode it continues fine but the problem there is it will ask for a Product key also breaking the unattended process.
the reason for starting into audit mode is so that after the installation has finished technicians can test the systems before they go through sysprep.
We had MDT 2010 running with no issues using litetouch. After updating to MDT 2012, we're now getting an error after the OS is installed. The machine reboots after Win7x64 is dropped and then the error below loops over and over until you kill it. This happens before any apps are installed. We've applied Update 1 and the issue continues. Any ideas?
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="11:37:20.000+000" date="09-17-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="11:37:21.000+000" date="09-17-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="11:37:20.000+000" date="09-17-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="11:37:21.000+000" date="09-17-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
Sorry this may have been asked many times around here but none directly answers to MDT 2010/2012.
How should be a TS set after running a Replace TS? In other words once I run a Replace TS which backs up to a share folder and all that good stuff. Now on my next bare metal machine how do I set the TS to restore the data?
I know I could simply set a TS to capture data (USMT3.x), then install OS and finally restore data (USMT4.x) which are three separate TS but how do you automate with two TS (Replace and Standard) built within MDT?
Thanks
Hi all,
This is my first post to please bear with me if I display signs of bad forum etiquette!
I have used MDT2010 in a small environment before but I have a client with a slightly different requirement.
Scenario:
The MDT2010 environment uses only a single deployment share.
The client does not want to use the MDT database (too much time spent maintaining contents)
The customsettings.ini file has the property JoinWorkgroup=WORKGROUP defined.
Requirement:
I want 2 task sequences.
One Task Sequence to build a workgroup computer and One Task Sequence to build a domain computer.
I do not want to use the Join workgroup/domain page in the MDT Wizard.
Question:
Where in the Task Sequence can I enter the settings so that the workstation joins the Domain (and thereby ignore the JoinWorkgroup=WORKGROUP setting in customsettings.ini?
I would like to do this for XP and Windows 7.
I am guessing that this can be achieved by editing either the sysprep.inf or unattend.txt files for the Task Sequence (accessed by using tje "OS Info" Tab in Task Sequence properties)....but I am not sure and would like some clarification.
Thanks in advance!
Hello,
My problem is when I being deploying to a set of 12 computers. 2 of them start the deployment processes, but the other 10 get the error below or just reboot without warning. After the first 2 get further in the deployment process I can get one or two more to start. And I repeat that until I’m done with the set of 12. Now it wouldn't be such a problem if I only had to deploy to just 12 or 20 total, but I have a total of 180 new computers to deploy to and only being able to deploy to 2 at a time is not very time efficient.
Wizard Error
A connection to the deployment share (\\servername\DeploymentShare$)
could not be made.
DHCP Lease was not obtained for any networking device! Possible
Cause: Check physical connection.
Abort
Retry
Ignore
What I would like to do is deploy to at least 20 computers at a time, if possible. Right now I'm going to try the 'Making WinPE Wait for Network in LTI Deployments' procedure at (http://blogs.technet.com/b/deploymentguys/archive/2009/09/23/making-winpe-wait-for-network-in-lti-deployments.aspx). Even though this procedure is for MDT2008 and is one of the fixes for MDT2010, I may just try it...
Any suggestions or help is greatly appreciated!!
Thanks
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”