Troubleshoot Remote Computers Using SCCM

If a company plans to update the hardware of the computer & IT systems, it might be a headache because all of these systems might not be at one place. Remote deployment of software is never easy. Moreover, along with the hardware change, you need to update or upgrade the operating system as well. Using SCCM is one of the easiest ways to get this done.

Machines can display errors, after logging in, if the machine is old enough and the operating system or any boot application has been corrupted. The system admin can look into the error remotely and check the cause of the error. Many a times, the error is caused by the permission setting in the proprietary or internal application folder.

If the error is not local and the problem is in all the computers, attending each of the machines individually is not an option. It would be impossible to change the permission settings of all the computers, especially if the computers are located all around the world. Instead, scripts like Microsoft's XCACLS.vbs can be used via internet to handle the situation. Here, SCCM or the System Center Configuration Manager comes handy. This is a freely downloadable solution from Microsoft and is on the official Microsoft site. The site is very helpful to the new users as well and all the documentations, including how to use it properly and all the advanced codes are present as well.

With the System Center Configuration Manager or the SCCM asset management tool, the system admin can load the script after proper modification so that each machine downloads the3 script automatically. Creating an unattended install is easy with SCCM as well and can be done from the command line.

Open a terminal and run "c:program name" /E /G "yourdomain.comDomain Users":M /q

It is easy to find all the switches which connect the target computers to the company network using these commands:

/E – It changes the ACL, better than replacing it.

/G yourdomain.comDomain Users:M – It grants permission to the Domain Users group to change the contents of the application's folder

/Q – It runs the script in quiet mode. This is an optional command if Verbose mode causes no problem.

Now the program would run once the user logs in and it will automatically execute to change the permission setting. This will take place once and before the user runs the application.

Visit to know more about windows application packaging