cotagag

Totally agree with Jörgen's solution. One more thing to consider here. Are you going to deploy images only remotely? Or are there locations in your environment where this is not possible for any reasons and where you will have to provide the image on a bootable external media media (dvd, usb stick)? Very low probability but still if so, then you should have in mind that usually software updates more often than you are going to update the image. And at every update of any of your software you might need to update and re-send the usb sticks with image. Good luck. Gabriel.

Hello, I will go with the assumption that you are using SCCM2007. I suppose you have very strong reasons to install your very big package from the share and not to distribute it directly with SCCM. Otherwise, I would recommend to distribute it with SCCM. The biggest benefit will be the possibility of reporting the status of deployment, errors in case of any, you will have the posibility to re-run in caz of failure and so on. Anyway, here is an article describing perhaps what you want to achieve: http://www.codeproject.com/Articles/247643/SCCM-2007-User-Interactive-Task-Sequence Regards Gabriel

Hello, I don't know if this is the best solution but I can tell you how would I do it. 1. Identify all the exe files of all your applications and write them in a text file, each exe file on a separate row). This will help you later to maintain the script. Or just add the lines in the same script, will be easier to manage the download to every machine. 2. Create a vbs script which reads the file line by line in a loop, and checks if that exe is running. You will find many examples on how to script that. Below one of them Dim Process, strObject, strProcess Const strComputer = "." strProcess = "OUTLOOK.exe" IsProcessRunning = False strObject = "winmgmts://" & strComputer For Each Process in GetObject( strObject ).InstancesOf( "win32_process" ) If UCase( Process.name ) = UCase( strProcess ) Then MsgBox "Outlook is running" End If Next 3. Make the vbs to exit with 0 if everything is OK or exit with an error code if a process is running. 4. Execute the vbs in a task sequence before the actual installation of the software. 5. Set to fail the task sequence if the execution of vbs fails (exits with anything else than 0) Hope this helps you.

Hakeem, make sure that your server has internet access. For testing allow full, unrestricted access. If this solves the problem then check if the proper ports are opened.

The conditions you are looking for are quite easy to be implemented in a task sequence logic. The only thing you will have to do is to find how to detect if certain version of Access is already installed in your target machine. You can use registry keys or even the path to access.exe to get the file version. You will find a lot of posts on how to detect if specific version of Access in already installed.Then add the installation of your Access package in a container in the task sequence and add the desired logic.

Hello Matt, Jst an idea. Why wouldn't you use the SCCM default functionality for your scope? For eaxample add a new condition to the collection which contains all your targets. Add a query which will allow targets to that collection only if they meet an additional condition (your flag). You could gather the information about your flag with software or hardware inventory. You could force a software/hardware inventory execution on your collection containing all your target servers before starting the deployment of updates. Hope this gives you some ideas. Gabriel.