YiannosG

Try this setup /s /v"/l*v log.txt /qn RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS" or msiexec /i "Symantec......msi" /qb /norestart Also if its an MSI you can add a package from definition, point out to the msi and it will create the installation parameters for you

Install SCCM Client Center and select client action, issue HW,SW collection and Update DDR. Or use Right Click tools to update these. This will speed up the process on updating the records.Might help

Each DP can have a PXE role on it. So when you Create an image at the central SCCM and distribute it at your DP, your DP servers will be able to run the image deployment. Note that there is a different between a distribution point and a secondary SCCM site. Read more here and see which one matches ur company so you can modify your SCCM environment. You can have the WSUS in SCCM download the updates and then create packages and use the distribution points as you can do with any ordinary program.

Yeap! MS uses the same technology for the setup and MSP files

That is correct. Thats my current step; eliminate all computer images and have one generic image, where depending on the model the drivers will get installed, and depending on the department a specific task sequence will start to deploy the application based on that department. You can install Distribution Points on some servers and have boundaries on it, so it will offer the package only to that specific active directory site/ network IP range. Then when you create the packages you can select which distribution points that program will be available and when someone request that file from ie.site B it will get it from the local distribution point in site B, with out using your WAN bandwidth!This ofcourse works the same with OS images Also you can integrate WSUS in SCCM and SCCM clients on the computers will know that your SCCM has a WSUS built in!

Erm ..... what settings do you have under

In the client computer under %WINDIR%\System32\CCM\Cache do you see your package? Is it downloaded fully?

ok at first look this will not work call \\domain\ so create a packet in SCCM. If your files are resign to \\domain\software\sap-gui\7.10\ then create a new package and for source folder point out to 7.10 folder. This will make it your working directory. Then create a program for that and for command put Install.bat then replace all call \\domain\software\sap-gui\7.10\ with just call %~dp0 ie call \\domain\software\sap-gui\7.10\IE-SAPFIX.bat to call %~dp0IE-SAPFIX.bat That should do! it let me know how it goes Cheers Yiannos

Dont know for sure since i dont use outlook at work but read this...Configuring Outlook Profiles by Using a PRF File and this one http://technet.microsoft.com/en-us/library/cc179062%28office.12%29.aspx Best of luck!

Sure! Of course when you deploy a program from batch file and your deployment fails at the second setup for example you will have to rerun the batch as a whole again...So you might need to consider that in case something goes wrong, your program can be rerun/repair so your users will not get an error and the execution stucks and you will have to do it manually. I guess this is what Niall is referring. Anyway this is the one i was referring.... start /wait Toolbox\BrandTools.EXE start /wait msiexec /i ProofKit.WW\Proof.el\proof.msi LAUNCHEDBYSETUPEXE=1 /qb start /wait msiexec /i ProofKit.WW\Proof.en\proof.msi LAUNCHEDBYSETUPEXE=1 /qb start /wait msiexec /i ProofKit.WW\Proof.ru\proof.msi LAUNCHEDBYSETUPEXE=1 /qb start /wait regedit /s Toolbox\wizkit.reg rd /S /Q "C:\Program Files\Wiz-Kit" start /wait msiexec /i Toolbox\PresentationToolbox.msi /qb /norestart Installation of programs, add a registry key and remove a directory ^ and for the .Net 3.5 deployment, after you have extracted the files as per MS instructions. start /wait msiexec /i MSXML6_x86\msxml6.msi /qb /norestart start /wait msiexec /i RGBRAST_x86\RGB9RAST_x86.msi /qb /norestart start /wait msiexec /i NETFX20_x86\netfx20a_x86.msi /qb VSEXTUI=1 /norestart start /wait msiexec /i NETFX30_x86\netfx30a_x86.msi /qb VSEXTUI=1 /norestart start /wait msiexec /i netfx35_x86\vs_setup.msi /qb VSEXTUI=1 /norestart start /wait NDP35SP1-KB958484-x86.exe /passive /norestart start /wait vstor30.exe /q Start /wait prevents all setup from running at the same time, instead it start the first one, waits to finish then goes to the second etc. One last thing though. If you are going to run them from DP directly you might consider using %~dp0 value infront of the command so it can run with UNC (\\server\<path>) cause batch files do not run by default. So...... Before i learn this small tip for batch files i used to select "requires drive letter" so it could map the SCCM share on the user computer in order to run "locally"

I will have to disagree on this one Niall. On our recent major upgrade of Office 2007 i had a problem with Proofing tools that was causing all language to be deployed and installing extra keyboard languages, which was not acceptable. To accomplish this i found the msi deployment for the specific 3 languages that i wanted and link them on a batch file. One thing let to another and i link a company based installation on that that required to add a registry value and delete a folder under Program Files. The batch worked flawlessly. To sum up, .Net deployment 3.5 SP1 could not run since if you run the full setup it will still require to access the internet which was causing problem. So as it was recommended you should extract it and then run 5-6 msi files which i linked each other to install .Net framework My 2 cents

Hmm doesnt seem to work

So you say that if i have it on Logon to run and change it now to rerun every 4 hours lets say, the new version will be installed on the ones that had the first version? will try...

I was wandering if there is a way to force an advertisement to re run if the program is on different version. For example the other day i created and advertisement to deploy a software update and after a half day i got a note that i needed to run an updated version since they had made a last minute changes. When i replaced the file and updated my DPs my program got noted down as version 2. The advertisement was marked to rerun if failed. Now since it was running for half a day, some users got the advertisement. Those users i am not able to run the version 2 since it got marked as program will not rerun due to already being installed. I was able to see that users where downloading the version 2 and that the advertisement got updated to version 2 but i couldn't rerun it on the ones that already got the file. Any thoughts?

Oh there is that post!! i knew i saw it here

You can delete the build part from the task sequence:) Follow Peters link

yeap! works flawlessly! Thank God cause we have a lot OUs

Follow this link! Create a collection and note the Collection ID Then Cscript.exe SystemOUCollectionCreator.vbs <ServerName> <ParentCollectionID> <site code> Voila!!

Is there a way to create a recursive query? Lets say use one query and get the Sub-OUs...and end up having your AD structure in SCCM?

Hello. Are you able to see the computer on the collection? If you go on the client computer in Conficuration Manager do you see the correct Assighnment code? Under Actions what do you see? Its the same as the guide?

Here! http://technet.microsoft.com/en-us/library/cc179662.aspx

Hmm i guess not since the profilename is different everytime right? You are going to use multiple users on the same pc? I dont have Outlook deployed on our company but check these two links and let me know if it helps... http://www.techimo.com/forum/applications-operating-systems/33124-default-location-outlook-pst-file.html http://technet.microsoft.com/en-us/library/cc179062.aspx

Maybe under [HKEY_USERS\.DEFAULT\ ?

Sure. Go to Software Distribution, Packages, Select your package and expand it. Select Programs on the left side and at the righr side you should see the list of programs that are set to run for the package. Double click that and thats the command

A quick search on the net shown that...Error 87 The parameter is incorrect. Ref : http://msdn.microsoft.com/en-us/library/aa368542%28VS.85%29.aspx can you please paste the package's program command line? i guess that parameter it's not compatible with WIN7