Peter33

Hi, the Setup.exe should be an Install Shiled Insataller. You can create a response file for a silent installation with the command line "setup.exe -r -f1".\setup.iss". With the response file you can create a simple program in the SCCM package "setup.exe -s". With the -s switch the setup will look for the setup.iss and run completely unattended. Just make sure you capture the iss file on a clean machine without any previous installations of your Remedy Client. This way you can avoid all the hassle of batch files and option files (which are place in the MDT script folder?).

Install the HP Software Framework before the package.

Set net = WScript.CreateObject("WScript.Network") local = net.ComputerName DomainName = "DOMAINNAME" UserAccount = "USERNAME/GROUPNAME" strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") set colOperatingSystems = objWMIService.ExecQuery _ ("Select * from Win32_OperatingSystem") For Each objOperatingSystem in colOperatingSystems 'GERMAN OS If objOperatingSystem.OSLanguage = "1031" Then set group = GetObject("WinNT://"& local &"/Administratoren") End If 'ENGLISH OS If objOperatingSystem.OSLanguage = "1033" Then set group = GetObject("WinNT://"& local &"/Administrators") End If Next on error resume next group.Add "WinNT://"& DomainName &"/"& UserAccount &"" This script works pretty fine. Just make sure to run it after Domain Join. You may probably cut the language selection part.

comment or delete the following line #Export-ModuleMember Set-on At the end of the script add a line like this and replace the exe with your application. Set-PinnedApplication -Action PinToStartMenu -FilePath "C:\WINDOWS\system32\notepad.exe"

We are using a single task sequence for all systems. The OU is chosen by a script which analyzes the IP address range. The script is holding an array with the OUs and the corresponding address range. Additionaly the OU can be changed manually with a drop down menu in the HTA frontend. So the central stuff can deploy machines before sending them out to other locations.

You even don't need the script. You can just run the 'gather' from MDT and then set the variable with %SerialNumber%. The gather will deliver some useful information about your system for finetuning your task sequence. For example applying drivers to several systems you can use the model variable which is read from the BIOS during gather. It's also telling you if the system is a laptop, desktop or virtual pc.

I suggest you to use a script for this task and write the output of each machine into an html file on a network share. Otherwise you would have to disable the software inventory for all other clients.

Make sure that the system discovery is covering the AD container where your machine is located. The maximum time should be the schedule of the system discovery + schedule of the collection update cycle.

A Package is also needed when you are using a task sequence, since you want to copy the setup source files to your systems. So i guess you mean a program instead of a task sequence. Of course, this is possible. Just put the 3 Steps in a batch file and the call the batch in your program. md "%programfiles%\app" xcopy.exe ".\*" "%programfiles%\app" /D /E /C /I /Q /H /R /Y /S pushd "%programfiles%\app" install.exe popd

Don't forget to fill the "start in" option for step 3 with "%programfiles%\app". The "cmd /c" is not needed for this step.

Hi Staudi, the mof file should look like this #pragma namespace("\\\\.\\root\\ccm\\policy\\machine\\requestedconfig") [CCM_POlicy_PartialPolicy(true)] instance of CCM_SoftwareDistributionClientConfig { SiteSettingsKey = 1; PolicySource = "Local"; //override only this property, all others from the Site/Management Point [CCM_Policy_Override(true)] Enabled = FALSE; };

You can still use the "command line" option from the general section and run it with a different account.

Do you want to install SP1 during OSD or for a running system? For OSD you should use Windows 7 sources with integrated SP1.

Hi Staudi, take a look at this.

I would use the pkgmgr.exe like described here.

The properties for the query you are looking for are in "SystemResource". For the first condition use "SystemGroupName" with the option "is not". For the second option use the property "Name" with the options "is like" wstn% lptp%. To add some logic you should also check if MS Project is even installed on the computer. Otherwise several hundred or thousend computers will receive the advertisement even if there is nothing to uninstall. So add another condition by using the AddRemovePrograms class queueing for the Product ID of your project version. The AddRemovePrograms table is filled by the hardware inventory of the clients.

Hi kevin, looks good this way if you want to install SAPGUI 7.10. Task sequences however are always non interactive and programs have to be set as non interactive as well to be usable in task sequences. The only way to get some interaction into a task sequence is HTA scripting. To show the users whats going on you can use the advertisement property for the task sequence progress. Thes progress bar itself is just reflecting the the the number of steps in the task sequence, in this case 3. It will not move until the installation is finished.

First create a group in your task sequence and put the first wmi query on this group. Give it a reasonable name. This group checks for an already existing installtion of 7.20 and skips everything if so. Next place another group under the first one (nested) and put the second wmi query on it. Also give it a name that points out the action in the logs. Don't forget to add the "if none" statements before the wmi queries. Under the second group place the installation. The installtion itself will run always under local system account.

Hi Kimounje, here you go. Both need an if statement with the option "none". Select * FromM Win32Reg_AddRemovePrograms Where DisplayName = "SAP GUI for Windows 7.20" Select Caption from Win32_Process Where Caption Like "SAP%"

Yes, we are using a single task sequence for all hardware models. You just need to use the ability of task sequences to run WMI queries on the local system. Create a new group for every hardware model and query the win32_ComputerSystem class for the property "Model" ( select * from Win32_ComputerSystem Where model like "%MYMODEL%" ). Then place the relevant configuration program in the group. This way you can also deploy hardware specific software packages to your machines, like power management tools for notebooks. WMI is your best friend in SCCM

Hi Cake, have a look a this link. This was helping to solve the caching problems for me when ran into the same issue.

Hi Cake, i would suggest to to check the IIS logs on your distribution point. There are several more file types. I don't remember them all now, but we had to white list some more. I think conf files are being blocked also by default. You should see the trouble makers in the logs.

What exactly did not work. The new client needs an SCCM client first which is usually done by push installations. Have you configured the the client installation in your SCCM Server?

Hi Cake, bin file are blocked by your IIS by default. You have to modify the mime types on all IIS on all distribution points and allow bin files to be transfered. Therafter retart the IIS. Otherwise you can also disable the local caching for this package as workaround.

Hi Adrian, yo have to update your distribution points when you change anything in the source files. You don't have to update them if you change program options in your SCCM package. The question is if you have even distributed your package to any distribution point. And never ever make changes in the packages of the distribution point itself, only in the source directory of your package. For office 2007 you can also use an xml file to trigger the hidden install. It's being called with the /config option.