GarthMJ

Your query is not written to limit the results to a collection. This sample query will get you started. http://sccmug.ca/2014/01/13/limiting-a-report-to-a-collection/ BTW, you will get interesting results with that query. aka you will get more than 1 IP address for a computer. Why not look at the built-in reports for this?

My quick look at this suggest the problem is with the script. Basically unless there is an encrypted file on Z:\ nothing will show up. So you need to go back to the drawing board and re-write you script.

Printer are a user setting, not a system setting. TS will run as the local system account, therefore you are adding the printer to the local system account and not the computer itself.

I would think that you could do this with a script and therefore create a SCOM rule for it.

What do you mean by this question? Are you trying to protect against a virus?

How would anyone else fix a problem with that software other than the vendor? Why wouldn't you contact them?

Contact the company that make it and tell them that there is a problem.

Computers will only download the SU they need, not the whole SU packages. If BranchCache is enable they will download it from a local computer (assuming it exist).

If setup correctly, even without a DP, this will use the same or less network bandwidth, than you do today with WSUS or worse yet to MS directly.

SCUP is used by most people. If you are looking for 3rd party tools and cost is an issue, then PatchMyPC is the only option.

This is not best practice. You should use the Computer or Network Access account to access the DP.

Yup that right.. You beat me to it. :-)

No that is not correct. You need to test your batch file using the PSexec to confirm that the batch file setup correctly. When you execute your batch file on your PC (or any other PC) does the batch file does what it should? My guess it that it will but for the LOCAL SYSTEM account. But that is not what you want, you want it for the locally logon user. Hence why you think that the batch file is failing when executed by CM. Once you confirm this step, you should be able to change the security context to the user security context and ultimately solve your problem.

You need to test your batch file using psexec -i -s batchfilename.bat command. This is how CM will run your batchfile.

Let me fix the typo above. Since CM uses the local system account to do just about everything, test your script using this process. https://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/, When it works using this process it will work within CM too.

What make you think that the batch file isn't running? What security context are you running the batch file as, user or local system?

There is not such docs as to when or how often you should or should not change the PW. HOWEVER if you change the NAA account your will likely lock it out for several hours or days. As such you should create two NAA accounts and change the PWs at different intervals. Also don't forget that if you change any of the SQL account that your MUST create the SPN record too. What do you mean by the CM Admin account? Exactly which account are you talking about?

Yes, I'm say you should use a Package/program for this. Your command as it sits will fail 100% of the time if you try to copy files using CMD. The reason for the failure is the UNC, When you execute the CMD it executes as local system. This account will NOT have access to the UNC and therefore will fail. This will NOT fail if you use a package/program, as long as the source files are within the package.

No it does not have any impact on SSRS reports.

Why not use the VPN logs to keep track of who uses VPN? Personally I would get rid of VPN and use DirectAccess instead.

What does your query look like? When you look at the All System collection can you see them? Do you have AD discovery enabled?

Why not make a package with the shortcuts?

Then you will need to use subselect queries http://www.enhansoft.com/?s=subselect Remember that QFE does not have all SU listed within (most but not all).

Change your "And" to "Or"

Have you tried it as an x86 cmd?