Creating a scripted installation for push down - Having a few problems after one of my post installation tasks!

Hi All,

I've recently been tasked with the implementation of the Dell Kace appliances 1000 & 2000 into our IT infrastructure and it’s fair to say that I’m really impressed with how simple it’s been to install and configure.

In the past we have used WDS (windows deployment services) to deploy our images to user laptops but this is long winded process and difficult to maintain in a sense that im forever updating our images by building them, capturing them and then finally deploying them. What I particularly like about the K2000 is that it provides huge amounts of functionality with its scripted installations and the driver utility is superb! 

Moving on to my question, I have so far created a Windows 7 x64Bit Image that does the following and works absolutely fine:

Joins the domain
Applies the computer name
Pushes down the K software
Activates Windows 7 
Installs Citrix Receiver Enterprise

Other software I would like to add to this scripted installation is Microsoft Office 2010, Siemens telephone software myPortal, PowerBroker for Desktops and Mimecast. The problem I’m having is that the scripted installation does what iv stated but any other tasks I add after the Citrix Receiver never seem to work.

To install the Citrix Receiver I’m using the following CLI command:

CitrixReceiver.exe /silent /noreboot

Could somebody explain why every time I add in other post installation tasks to my scripted installation only the Citrix Receiver installs? I know this is vague but it’s pure and simple, no matter what command line I use for the other software packages they never install after the Citrix Receiver.

Thanks in advance,




0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: dugullett 7 years ago
Red Belt

More than likely it's failing at the activation of Windows 7. Did you upload a .bat as an application? If so make sure you are calling the .bat in your command line.

Also can you upload the install files found at C:\Kace?

Posted by: andrew_lubchansky 7 years ago
2nd Degree Black Belt

It may be possible that you need to perform a reboot following Citrix Receiver before the OS will allow any other installations to continue.  You will need to use the Post Install Task Converter found here: http://www.kace.com/support/resources/kb/article/k2000-postinstall-task-converter

Also, you may want to check some of the best practices found here: http://blog.kace.com/2013/03/08/k2000-kloser-look-best-practices/

Have you tried pulling out the Citrix Receiver and find that everything installs fine with that out of the install list?  Sometimes just moving the order around helps to reduce possible incompatibilties and the number of reboots needed.

  • Thank you very much for the links - Iv taken a look at the Kace website in the past but I have to admit its not the easiest to navigate and find things :) These are really helpful though - Thanks! - k4rl@TES 7 years ago
Posted by: nheyne 7 years ago
Red Belt

Or you could just make sure the Citrix Receiver postinstall is last maybe?  Our postinstalls are very similar to yours, join domain, install kace agent, then whatever else we need done.  Once we incorporated the postinstall task converter Andrew mentions above, we never had a problem.

  • Not a bad idea. Just a note, that I always liked having my KACE Agent coming down last, so that its first inventory was complete. - andrew_lubchansky 7 years ago
    • Il take this on board!! Thank you :) - k4rl@TES 7 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ