GarthMJ

Use the built-in reports.

The client is already installed on that PC, so there is nothing wrong. Have you logon to the PC to look at it?

What wrong with using the built-in report for this called, Compliance 8 - Computers in a specific compliance state for an update (secondary)?

Yes that is correct but you really should hire a senior consultant to help you with the design. There is a lot more to CM that what you have listed.

You real should use the method listed here. http://www.mnscug.org/blogs/sherry-kissinger/330-internet-explorer-version-information-via-hardware-inventory

Have you looked at the built-in reports for this?

Take a look at this blog post. http://www.enhansoft.com/blog/grant-non-sccm-2012-administrators-the-right-to-createmodify-sccm-2012-ssrs-reports

The idea for removing the RD line is so that you can figure out exactly why you are getting the error message.

Hi I asked around in a private mailing and it is supported to Restore CM with Intune. Here are the two notes that I got on the subject. Recreate the Microsoft Intune Subscription If you recover a Configuration Manager site server after the site server computer is re-imaged, the Microsoft Intune subscription is not restored if it was previously installed. You must recreate the subscription after you recover the site. For more information, see Configuring the Microsoft Intune Subscription. Funny you should mention this as I had a discussion with one of our PFEs about this the other day. As far as I know it’s supported but it does have some known issues. The restore process doesn’t restore the certificates needed by Intune so you will need to reinstall the Intune Connector role. I don’t remember if it’s also necessary to remove/re-add the subscription in the console. So.....

Start by getting rid of the last line of the batch file Replace C:\Window with %windir% On the system in question, make sure that inst_cap.exe exists

The error above 2147942402 = The system cannot find the file specified. So, which line of you batch is generating this error?

No there is no way to do that.. Generally it will be no more that 24 hours out of date.

First work on the install and make sure that you are happy with that. The uninstall if a lot bigger problem and I question the need for it to be automated. Why you ask because, How exactly do you determine who it should be uninstalled from? What exact is your decommissioning process for a PC? What exact is the replacement staff process? How exact is primary user configured? Without these questions (and more) being answer you can easily create a process that will cause you more headaches then it is worth.

Why do you want to deploy it to computer but target users? Why aren't you just targeting it users? Why make your life difficult?

ok, that should work. Why do you think that it does work?

The answer is , "it depends". Are you using application? How many different deployment types are you using? which deployment type are you using? Do you have the primary user details configured?

And was it the Firewall?

If I remember right, and I'm not saying I do, but quote marks might mean it is a string and not a number. Therefore it will not convert the exit code to hex.

Did you try? if intret = "0x40000101" or intret = 1073742081 then

Did you turn on the content validation feature?

Your best bet for this is to write a SSRS report for this. Or even a SQL query. What exactly are you trying to do?

Ok I will ask, why do you want to do that? You do know that even if you schedule this, it will automatic run once an hour for 7 days or until the client is installed. So what exactly are you hoping to control?

Turn on automatic push, this will attempt to install the client on all computers that don't have the client.

So a Package would be easier but you can do it as a application too. You would need to set it up as a Script application. This trick is where you call the MSI from. By default if you don't give it a path it will try to execute it from the local directory, aka from the same directory as your powershell script. By doing it this way you remove the network issue, you have created within the script above. For example http://www.enhansoft.com/blog/using-sccm-2012-application-model-to-install-cmtrace-file-version http://www.enhansoft.com/blog/using-sccm-2012-application-model-to-install-psexec

Why are you trying to run the MSI from a server share and not as part of the package? This will cause you a lot of headaches and it complete defeats the purpose of CM12.