Purpose: another fundamental thing to know when creating a Custom Detection script in SCCM 2012
After you have understood how to use Custom Detection Method in SCCM 2012, you will discover multiple ways to use it efficiently in you deployments. One such way is to use Custom Detection Method with a User Profile variable. However, there is a catch how to do this.
Purpose: You want to copy a predefined file to the currently logged on user personal network folder with SCCM
You might find yourself in a situation where some of the applications have been installed in one way and the others in another way. Depending on the problem, you might just want to clean the table and reinstall the the applications with your definitions. If this is not possible or would not be cost efficient, you could use SCCM to check if “something” exists and alter the workstations where this something is missing. In this example this “something” is a missing configuration file located in the personal network folder of an user.
Usage: cscript.exe IT_APP_VBS_CopyFileToNetworkedPersonalFolder.vbs
Configuration: You need to insert your own PREDEFINED FILE and LOCATION.
Purpose: Remove a predefined file from every actual user profile folder in a workstation.
In a scenario where you have delivered files to every or some user profiles of a workstation, you need to iterate through the C:\Users\Public\ -subfolders to reach your files. Of course this can be used as well against something that you have not delivered at all. These scenarios can be faulty application shortcuts directly in user desktop, user based configuration files in AppData -folders or similar.
Usage: cscript.exe IT_OSD_VBS_RemoveAFileFromEveryUserProfile.vbs (no parameters exist)
Configuration: You need to insert the file that you want to remove to strFolderPathLocal
Purpose: Allow non-administrator / limited user to install fonts in W7 with UAC turned on
Since the Windows 7 operating system has been published, the Web has been full of questions about how to allow limited users to install fonts in a corporate environment. There are not many ways available, unless you really want to lower the security of your OS and change the way the OS is supposed to work. However there is at least one way to allow this: first you need to change the way you have tried to approach this problem. You can install the fonts to a user session instead of the local machine. You will need to create a system that will make sure that the fonts are kept in the user session even after a system reboot or for another user.
Configuration: You can change the location of the Public Fonts -directory, if it pleases you.
Purpose: Create a shortcut in the current user desktop and current user Start Menu, defined by user
In corporate environments, standard users rarely have permissions to edit shortcuts for a workstation for all the users. You might come up with a scenario where you need to give users permission to create shortcuts for an application. Most importantly, the shortcut actually needs parameters to work correctly. To reduce the amount of Help Desk calls, you can create a script that creates the shortcuts correctly for the current users by asking the parameter. The parameter can be a server, http-address, profile name, application environment, and so on. This script is extremely helpful in a situation where the System Administrator might not know what parameter each user is actually using or creating all the different scenarios for users might not be cost-efficient. This of course requires that the users know which environment they are using, or this will not work as intended.
Usage: cscript.exe IT_APP_VBS_CreateShortcutsFromUserInput (User Input Required)
Configuration: You need to change the configuration in “Configure the script” -part of the code.