Manny-Tech Posted October 21, 2015 Posted October 21, 2015 I'm just branching into MDT, I used it some years ago at a previous company but this time around it's all my own config. I have a network share with the majority of our applications, rather than me duplicating this all to the Applications folder on the Deployment Share, I was hoping to use the option of 'Without Source Files or Elsewhere on the Network'. I'm trying to deploy Office 2013. I have the command set as "\\servername\applications$\Office 2013\setup.exe /adminfile office2013.msp" with a working directory of "\\servername\applications$\office 2013" Each time it runs I get an error of 'Unable to set working directory' and 'Application Microsoft Office 2013 returned an unexpected return code: 2.' Just for my own peace of mind I will copy it to the Deployment Share just so I know it actually installs, but I'm struggling to find examples of people using the 'Without source files' option successfully.
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 I can confirm it works fine when it's in the Deployment Share Applications folder. I guess the problem is when connecting to a network share when it uses the local adminstrator account, I think at the start of the wizard it asks for a username and password for connection to network shares, which I used mine so there shouldn't be a problem there.
sted Posted October 21, 2015 Posted October 21, 2015 does the user you specify in mdt either manually or in customsettings.ini have access to the share with the software on?
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 The user in MDT is my account, I'm a domain admin and have full access to the share.
sted Posted October 21, 2015 Posted October 21, 2015 aha "\\servername\applications$\Office 2013\setup.exe /adminfile office2013.msp" with a working directory of "\\servername\applications$\office 2013" youve got your "'s wrong should be "\\servername\applications$\Office 2013\setup.exe" /adminfile "\\servername\applications$\Office 2013\office2013.msp" with a working directory of "\\servername\applications$\office 2013"
computer_expert Posted October 21, 2015 Posted October 21, 2015 (edited) What happens when you put the full path to the MST in the command? "\\servername\applications$\Office 2013\setup.exe" /adminfile "\\servername\applications$\Office 2013\office2013.msp" Alternatively you can put the MST into the 'Updates' folder within the source office files and leave the adminfiles switch off. The office installer looks for the msp in the updates folder before installing so should pick it up. Make sure that the account you use to log into MDT (at the very beginning of the deployment process) has a minimum of read only access the network share where the installers are located. This is the account MDT uses for any network resources. Edited October 21, 2015 by computer_expert
Arthur Posted October 21, 2015 Posted October 21, 2015 Try adding the UNC path to the MSP... "\\ServerName\Applications$\Office 2013\setup.exe" /adminfile "\\ServerName\Applications$\Office 2013\office2013.msp" If that doesn't work put the MSP in the 'Updates' folder and then running Setup.exe without any parameters. Edit. What @computer_expert said.
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 It still fails, I will attach the ZTIApplications log file. Is there any other log files I can look into? I have double checked permissions on the share, I have full access. I'm not sure why, in the log file, that it says it's connection to \\servername and then says it failed to connect to \\\servername (note the three backslashes).ZTIApplications.txt
themightymrp Posted October 21, 2015 Posted October 21, 2015 Opening that log file using CMtrace show the following in red. Have you edited the log file before posting to hide the name of the server? If not it is trying to find a server called SERVERNAME! Also, it says that it is trying to connect without a username
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 I did do rather than explaining that it was called something else. I don't understand why it is trying to connect without a username? Where else can I set this if it isn't mine at the start of the wizard?
themightymrp Posted October 21, 2015 Posted October 21, 2015 Where exactly are you specifying the username and password? Is it in the task sequence itself or is it at the opening page when you boot from PXE and you have to login before it lets you see the list of task sequences?
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 It's when you boot from PXE before you see the task sequences.
themightymrp Posted October 21, 2015 Posted October 21, 2015 If you go to the properties of the deployment share itself within the MDT console, under the Rules tab click on Bootstrap.ini Have you got a value specified for DeployRoot= ? If you have used the variable %WDSServer%\deploymentshare you can get errors when your applications are in other shares. Specify the name of the server instead i.e. DeployRoot=\\servername\deploymentshare You can also just try commenting out the line with a # at the beginning
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 [settings] Priority=Default [Default] DeployRoot=\\srvwds1\deploymentshare$ SkipBDDWelcome=Yes UserID=username UserDomain=domain.school UserPassword=password KeyboardLocale=0809:00000809 UserLocale=en-GB Countrycode=44
themightymrp Posted October 21, 2015 Posted October 21, 2015 OK then, not that. Try this. Put the msp file inside the Updates folder (as mentioned a few times above). Re-add the application using the 'without source files' option again. This time set the command to be just setup.exe , nothing more. Set the working directory to be "\\servername\applications$\office 2013" See if that works
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 (edited) I'll give it a go now. It is consistently saying on the deployment summary that it is unable to map a network drive to \\\servername that being the 'elsewhere on the network' server. Edited October 21, 2015 by Manny-Tech
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 Yep - still the same, I tried with another app too and it seems to be a problem connecting to the share rather than the command to run the app itself. I don't get what more I can do when I have tried with a domain admin account that has access to all shares.
themightymrp Posted October 21, 2015 Posted October 21, 2015 Have you got any credentials specified in the customsettings.ini file?
Manny-Tech Posted October 21, 2015 Author Posted October 21, 2015 (edited) Below is the CustomSettings.ini. Username and password are my domain admin credentials. The only other thing I can think to do is set a command in the TS to map a drive and run the application - I was hoping not to do that though. [settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y DomainAdmin=username DomainAdminPassword=password DomainAdminDomain=school.domain JoinDomain=school.domain SkipAdminPassword=Yes SkipProductKey=Yes SkipBDDWelcome=Yes SkipApplications=No SkipCapture=Yes SkipComputerBackup=Yes SkipBitLocker=YES SkipDeploymentType=Yes SkipDomainMembership=No SkipPackageDisplay=Yes SkipUserData=Yes SkipWizard=No SkipSummary=Yes SkipFinalSummary=No SkipTimeZone=Yes SkipLocaleSelection=Yes WSUSServer=http://SRVWSUS:8530 UserDataLocation=None FinishAction=Restart AdminPassword=Password Countrycode=44 TimeZone=085 TimeZoneName=GMT Standard Time UILanguage=en-GB UILanguagefallback=0809:00000809 KeyboardLocale=0809:00000809 UserLocale=en-GB InputLocale=0809:00000809 SystemLocale=0809:00000809 BitsPerPel=32 VRefresh=60 XResolution=1 YResolution=1 Edited October 21, 2015 by Manny-Tech
themightymrp Posted October 22, 2015 Posted October 22, 2015 Just for my own peace of mind, when you re-added the application using my suggestion above, did you adjust the task sequence with the new GUID for the app? It looks like from your posted log file that you have it as a mandatory app. Correct me if I'm wrong. The only other thing I can think of is to open the help file from within the MDT workbench and search for "Connecting to Network Resources". There is a particular ZTI script you can add in to the task sequence as a step BEFORE the install applications stage which should forcibly connect to a UNC share on another server. Read the file for exact usage and syntax
Manny-Tech Posted October 22, 2015 Author Posted October 22, 2015 With the help of @themightymrp we have managed to narrow it down to this problem only occurring when the machine is joined to the domain. The connection to the share works perfectly when connected to a workgroup. What I did notice that whilst it was performing its first boot after OS installation was that it seemed to join the domain during the 'Applying System Settings' stage, just after 'Configuring Devices'. Once it logged in with the local admin rights I always got a 'This computer needs to restart' sort of prompt, at the time I just thought nothing of it considering that during my TS it restarts the machine many times, just not between domain join and installing applications. @themightymrp recommended just dropped a restart in there which has sorted it. There are two options, well three actually, you either 1) add a restart after domain join before installation of applications 2) move the domain join after the applications installs or 3) leave domain join off altogether and do it manually. Anyhow, many hours of frustration are over and I can continue with getting machines built! Thanks for all the input 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now