jimlock720
asked on
Deploying Dell R310 and Dell R510 Servers with MDT Problems
I have several task sequences set up to build and deploy vmware images using MDT 2012 and those work great. I also have a need to do similar deployments to physical Dell PowerEdge boxes, mostly R310, R510 and R620. All of them have idrac cards with the lifecycle controller installed.
What I have been doing is this (in a nutshell): Map the LiteTouchPE_x64.iso image to the idraq and select "attach", enter the lifcycle controller's 'deploy OS' section and configure the raid controller then allow it to connect and run the mounted ISO image. Static addresses are put into the MS wizard, the os is selected then I tell it to go.
While the OS image (usually either server 2012R2 or server 2008R2) itself ends up on the target system successfully, I am seeing errors when the MDT script tries to install .net3.5 and run "run command line" tasks. The whole thing errors out and never does updates. This exact same task sequence works great for a vmware vm but not for dell boxes.
It stands to reason that I am missing something. What am I doing wrong that the Dell boxes don't "like"? If someone has an unattended.xml and ts.xml would be handy but minus those, someone please give me a clue as to how to configure the task sequence so that it works like I expect it to such as patch updates and various settings I have put into the sequence. Thanks in advance.
What I have been doing is this (in a nutshell): Map the LiteTouchPE_x64.iso image to the idraq and select "attach", enter the lifcycle controller's 'deploy OS' section and configure the raid controller then allow it to connect and run the mounted ISO image. Static addresses are put into the MS wizard, the os is selected then I tell it to go.
While the OS image (usually either server 2012R2 or server 2008R2) itself ends up on the target system successfully, I am seeing errors when the MDT script tries to install .net3.5 and run "run command line" tasks. The whole thing errors out and never does updates. This exact same task sequence works great for a vmware vm but not for dell boxes.
It stands to reason that I am missing something. What am I doing wrong that the Dell boxes don't "like"? If someone has an unattended.xml and ts.xml would be handy but minus those, someone please give me a clue as to how to configure the task sequence so that it works like I expect it to such as patch updates and various settings I have put into the sequence. Thanks in advance.
David Johnson, CD
how are you trying to install the .net packages? using powershell add-windowsfeature / dism /online /enable-feature /featurename:<feature name> adding the feature in MDT itself?
ASKER
It is being done like this:
It, along with vmware tools, shows up as a list at the startup boot iso. I deselect the vmware tools for a physical build. windows firewall and RDP are both successfully enabled using a powershell script.
It, along with vmware tools, shows up as a list at the startup boot iso. I deselect the vmware tools for a physical build. windows firewall and RDP are both successfully enabled using a powershell script.
[Settings]
Priority=ByVMType, Default
Properties=MyCustomProperty
[Default]
OSInstall=yes
[ByVMType]
Subsection=IsVM-%ISVM%
[IsVM-True]
Applications001={0b41ce2c-03a2-49c6-a129-2f6f9e5925ea}
.net 45 is incorrect correct version below:
VMPlatform = Hyper-V for Microsoft Hyper-VVMPlatform = VMware for VMware vSphere
VMPlatform = Xen for Citrix Xenserver
VMPlatform = VirtualBox for Oracle's VirtualBox
ASKER
I uploaded the wrong screen shot. This is how .net3.5 is installed now.
Why the info on AD structure? Is that needed to prevent the errors I am seeing?
Why the info on AD structure? Is that needed to prevent the errors I am seeing?
ASKER
OK guys here are the error codes I am getting:
Any ideas?
Any ideas?
ASKER
UPDATE - I removed the task to install .NET3.5 and the entire script ran perfectly. I don't get why that one task would be hanging up the whole thing but apparently it did. I checked the log and it complained about a path to the sxs folder not found but I mapped that exact path and it works fine.
what do you mean you mapped the path to the SXS folder.
ASKER
The sxs folder on the MDT server in the MDT share has to be accessible by the running script. In this case it is located here:
E:\MDT_Deployment\Operatin
The smsts.log log and ZTIOSRole.log both indicated an error when the script tried to install .net 3.5 (I know it's out of date but we have a requirement for it). The error was "path not found" which to me means it was looking for something in the sxs folder and wasn't able to find it.
I told the script not to bother installing .net at all and that resolved this error. I do need to find an automated way to install .net 3.x and 4.x though, preferably in the script prior to updates being applied.
E:\MDT_Deployment\Operatin
The smsts.log log and ZTIOSRole.log both indicated an error when the script tried to install .net 3.5 (I know it's out of date but we have a requirement for it). The error was "path not found" which to me means it was looking for something in the sxs folder and wasn't able to find it.
I told the script not to bother installing .net at all and that resolved this error. I do need to find an automated way to install .net 3.x and 4.x though, preferably in the script prior to updates being applied.
ASKER
So anyway, I mapped the folder as a drive on the target system (after it was up and running) and it worked just fine. That tells me that a file in that folder that is used to install .net is missing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.