jkabaseball

For OSD we have different task sequences depending on the role of the PC and what the user will be using it for. They are all deployed to unknown PC's and the tech simply selects the task sequence they wish to use.

I use something similar. I have collections just for installing applications. I use SCCM injector to add computers to the collections. It works well, but you see every collection and can add to any collection. I am going to give it a try with an intern and SCCM 2012 next week some. I'll let you know what I end up doing.

The serial number can be pulled from the BIOS. How do you plan on getting the campus and T/S? Without a way for SCCM to look up and figure out if serial number XXXX is a T or S and also what campus it is on, I think the best idea would be different task sequences. Then the task sequence just needs to figure out the serial number it can pull from the BIOS. The other option would be manually putting the PC Name in while you are selecting the task sequence. Then you can have one task sequence that will pull the PC name from the variable you typed in.

What I did was move my 2007 server to use IP Range instead of AD Site boundry. I grabbed a chunk of IP address and added that boundry to CM 2012 and use that to test. All the rest of the IP Range is in the boundry for CM 2007. On the CM 2007 I added the IP ranges and then deleted the AD Site so I had a few seconds of overlap in case a client was trying to check in. I wanted to make sure that there was some kind of boundry when it went to check in that it would fall into that boundry.

I know you need all 3 MSI's installed for Quicktime to work. The other idea would be an application with relationships to all 3 MSI appliactions. I haven't tried it, but the relationships I have tried have been sucessful. I don't see why it wouldn't work here.

we have it running in VMWare just fine.

I use a batch script and deploy it in a package. Here's my batch script: start /w msiexec /i %~dp0AppleApplicationSupport.msi /quiet /passive /norestart start /w msiexec /i %~dp0QuickTime.msi /quiet /passive /norestart ASUWISINSTALLED=0 APPLEAPPLICATIONSUPPORTISINSTALLED={0C34B801-6AEC-4667-B053-03A67E2D0415} DESKTOP_SHORTCUTs=NO QT_TRAY_ICON=NO SCHEDULE_ASUW=NO delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /v "QuickTime Task" /f I have version 7.7.1 (1680.42) Deployed in SCCM 2007 and 2012 no problems.