If it is an actual Package in the SCCM sense and not a "package" in the general sense then you need to use a script. I had to use this during the days of Altiris at a customer while i migrated them over to SCCM. This isn't pretty but it gets the job done.
YOu need to get the ADDSTools so you can use the DSQuery:
REM Check Machine OU for NO UAC
for /f "delims=* usebackq" %%a in (`@Z:\Microsoft\ADDSTools\dsquery computer -name %Computername%`) do @set computer=%%a
set ou=%computer:"=%
set ou=%ou:*,OU=OU%
IF "%OU%" NEQ "OU=Laptops,OU=Computers,DC=<domain>,DC=com" (goto :error) ELSE (goto :success)
if %errorlevel% NEQ 0 goto :error
goto :end
:success
Exit 5550
:error
Exit 5551
:end
Exit %errorlevel%
It basically checks the machines OU and says "if it isn't in this OU error out, if not run something. You can change the custom error codes and add your install command line into the ":success" section.
If it is an application (which you should really be putting all things into apps now with the new model) then in the application itself do the following:
- Open your deployment type
- click the requirements tab
- click add
- change the category to device
- change the condition to Organizational Unit (OU)
- change the rule type to value
- change the operator to one of
- click add
- click browse
- find ou and click ok
As you can see, the application model is amazingly easier than the package model was so it is definitely the desired method of deployment
Dustin Estes - MCP | www.dustinestes.com
