I've created a couple managed installs that won't deploy correctly.  I've run both manually and have been successful in each.

1.  .NET v3.5 Offline Install (http://support.microsoft.com/kb/2785188)

        Custom inventory:  "DirectoryExists(C:\Windows\Microsoft.NET\Framework\v3.5)"

        Uploaded the sxs folder and everything inside to our network share that domain Computers have full control

        Managed Install:  installation command "start /wait Dism.exe /online /enable-feature /featurename:NetFX3 /All             /Source:"\\networksharename\Software Deployment\Kace\sxs" /LimitAccess"  Run command only is checked,             Don't prepend msi is checked

      

2.  Microsoft Dynamics Nav 2009 R2 (trying to deploy "Classic" and "RTC" together with the config.xml)

         Custom Inventory Rule:   DirectoryExists(C:\Program Files (x86)\Microsoft Dynamics NAV\60\Classic) AND

                                              DirectoryExists(C:\Program Files (x86)\Microsoft Dynamics NAV\60\Role Tailored Client)

         Uploaded Install.bat:  

@echo off

 

IF EXIST "%PROGRAMFILES(X86)%" (GOTO 64BIT) ELSE (GOTO 32BIT)

 

:64BIT

 

mkdir "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming"

 

mkdir "C:\Windows\SysWOW64\config\systemprofile\Desktop"

 

mkdir "C:\Windows\SysWOW64\config\systemprofile\Favorites"

 

mkdir "C:\Windows\SysWOW64\config\systemprofile\Documents"

 

mkdir "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates"

 

mkdir "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo"

 

mkdir “C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu”

 

mkdir “C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup”

 

"\\NetworkShare\Software Deployment\Kace\NAV 2009 R2 Install\setup.exe" /quiet /config "\\NetworkShare\Software Deployment\Kace\NAV 2009 R2 Install\NavR2Config.xml" /log "C:\Navlog.txt"

 

goto END

 

:32BIT

 

mkdir "C:\Windows\System32\config\systemprofile\AppData\Roaming"

 

mkdir "C:\Windows\System32\config\systemprofile\Desktop"

 

mkdir "C:\Windows\System32\config\systemprofile\Favorites"

 

mkdir "C:\Windows\System32\config\systemprofile\Documents"

 

mkdir "C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates"

 

mkdir "C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo"

 

mkdir “C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu”

 

mkdir “C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup”

 

"\\NetworkShare\Software Deployment\Kace\NAV 2009 R2 Install\setup.exe" /quiet /config "\\NetworkShare\Software Deployment\Kace\NAV 2009 R2 Install\NavR2Config.xml" /log "C:\Navlog.txt"

END  

 

 

Again, both do what they're supposed when run manually.


Any help, tips, suggestions or anything of the sort will be greatly appreciated.  

 

 

 

0 Comments   [ + ] Show Comments

Comments

  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
Please log in to comment

Answers

1

Managed installs run under the system account so they do not have access to the network. It's better practice to include all of the necessary files for the installation in a zip and KACE will extract the files before running the installation command.

Answered 10/21/2013 by: chucksteel
Red Belt

  • I tried that as well for the .NET 3.5, but it didn't work. You can see that it tries to run the command, but the cmd window closes right away. I also turned on debugging, then ran the MI, but the errors it through were real general.
    • What are you using for the path to the sxs files? You might need to hard code the c:\programdata\dell\kace\downloads\<id>\sxs path, where <id> is the id of the software title you created.
      • I was using C:\Program Data\Dell\Kace\Downloads\12689\sxs which is what I believe you were suggesting.
      • I just saw that you have "Run command only" checked. KACE won't download the files to the client if that is checked.
      • I only had "run command only" checked when I was trying to run it from the network
      • I would try running the command manually on a machine after it fails (Assuming you don't have KACE set to delete the files).
      • When I run it manually it works, it opens the command window and it stays open until it completes the feature upgrade. I will try one more time and let you know if anything has changed.
      • Added a picture at the bottom of my original question of the manually run success
      • This might be one of the few things that the system account can't do. Try opening a command prompt as system using psexec and see if the command works:
        http://blogs.technet.com/b/askds/archive/2008/10/22/getting-a-cmd-prompt-as-system-in-windows-vista-and-windows-server-2008.aspx
      • That worked as well, see photo above...
      • You have to specify -s or it runs under your account. I don't see the -s when you launched psexec.
      • I'm sorry, added new snip... Is that correct? Ran as system and still completed successfully...
      • Wow. I'm really not sure what's going on. The only other thing I can suggest is putting the command in a install.cmd file and calling that instead. Maybe there's something about the command that isn't getting passed correctly when KACE runs it.
      • I've tried that too, it's really making me crazy not being able to figure it out!!! Do you know a way to force the cmd window to stay open until the cmd is finished running? Start /wait didn't work
      • If you add a pause statement to the end of your install.cmd that should force the window to stay open until a key is pressed.
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
1

I use Network Shares exclusively for Managed Installs as they are easier to update and manage. The SYSTEM account does have access to the network, but you must make sure that "Domain Computers" has rights to the share from where you're installing from. There is also a bonus of not needing to download and leave behind big installers, like for Creative Suite 6 or Autocad. 

Here is an example of my .Net 4.5 Installer CMD. Under the new version of KACE, CMD may not work right, and you'll have to convert to BAT format, which shouldn't matter for this particular installer. 

Let me know if you need any more info. 

___________setup45.cmd_____________

net use r: /delete ;removes any drive mapping to r:

net use r: "\\SERVER\installers\.Net Framework" ;maps network drive to the correct location

start /wait r:\dotnetfx45_full_x86_x64.exe /q ;Command that executes silent installer for x64 bit

net use r: /delete ; cleans up drive map

 

Answered 10/22/2013 by: archangel michael
Orange Belt

  • Can you comment more about cmd files not working right under 5.5? Is that a known issue?
    • I don't have 5.5 installed yet, but I hear that CMD files do not work as is in 5.5.

      I hear the following works. Rather than calling the install.cmd directly, you format the "run" command this way. I am about to test this on a couple minor installer scripts, as I need this to work correctly by the time we get to 5.5 (Thanksgiving week). I'll report back if this is an acceptable fix.

      cmd /c start /w install.cmd
      • Need to add "exit" to the CMD to properly close out the CMD window. Other than that, using this format should work.
      • We upgraded to 5.5 a couple of weeks ago and I haven't seen any issues using install.cmd with managed installs. I'm wondering if there are certain cases where they won't work, but as of right now I haven't seen any managed installs fail.
  • Michael, I have tried your suggestions and it seems to work manually, but again won't run as a managed install. I would like to discuss this a bit further in detail and I was hoping you may be able to assist me... If you can at any time in the near future, let me know and/or send me a chat request as I just added email to my profile.
Please log in to comment
Answer this question or Comment on this question for clarity