Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Require file before installation

  • Thread starter Thread starter pcb
  • Start date Start date
  • Replies Replies 4
  • Views Views 4K

pcb

Well-Known Member
Messages
45
Solutions
2
Reaction score
0
Points
6
Hello, we are trying to install an update to an application that may or may not be present on the client and if it isn't deploying the update to that client results in a failure that is not really a failure. I'd like to set a requirement that one of the application's files be present on the client before install is attempted. Is there a way to do this?
 
Hello, we are trying to install an update to an application that may or may not be present on the client and if it isn't deploying the update to that client results in a failure that is not really a failure. I'd like to set a requirement that one of the application's files be present on the client before install is attempted. Is there a way to do this?
Are you deploying it as an app or prog? If it is an app what is your detection method?
 
We are in the process of transitioning from Zenworks to MECM and our certificate for Zenworks expired leaving many of our clients disconnected. So this is really just a certificate deployment to the root store. The detection method just looks to see if the registry key that is added by the updater, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\ROOT\Certificates\950F6E..., exists. However, the Zenworks client isn't installed on every workstation in our network and the "updater" (exe created by MicroFocus) won't install the cert if Zenworks isn't found. This throws an error or times out. So we just want to detect if Zenworks is present on the box before attempting the install. In the deployment type, requirements tab, I don't see anything that allows requiring a file or registry key to be present on the system before install is attempted. This seems like a basic feature that is missing... but then I am used to Zenworks where I can detect just about anything and set it as a major or minor requirement for install.
 
I think I have this figured out. You have to create a custom requirement. It confused me when I looked at this option as the list was already populated with dell command options. Clicking create allows you to create the file requirement. Testing now.
 

Forum statistics

Threads
7,163
Messages
27,960
Members
18,251
Latest member
Twc

Trending content

Back
Top