Child site software deployment question

Good afternoon, otherwise there it is:)

I've got one parent sites and some of connected child primary sites. In many of times i don't want to let branch's admins deploying software from packages that i've maked in Parent Site office. After replication there are objects's with 'lock' in branch's console, admins simplely distribute this package on their DP's on deploy to the clients. How can i reject it. Thanks in advance.

July 1st, 2013 3:51pm

AFAIK... You can't in 2007.
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2013 4:18pm

Could you explain it, John. I thougt the explantation should be.....There is not good.....If all child's come get and can deploy everything from Parent...it contradicts to logic. Please correct me if a'm wrong....
July 1st, 2013 4:47pm

John is correct and it doesn't contradict logic at all -- that's just how it works. Child sites aren't about restricting access to content, they are about making content available from a central location and allowing the child site admins control over deploying that content.
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2013 5:01pm

Hi Futsal

When you create a Software Package in SCCM 2007 , you can set permissions on that specific instance or for entire class. Say suppose if you do not give the Branch Admins "Modify" permission on the packages, they shouldn't be able to distribute the package to their DPs.

Please check this: http://technet.microsoft.com/en-us/library/bb632791.aspx

Hope this helps

Regards,

Manohar Pusala

July 1st, 2013 5:02pm

In my case there is only central site admins print in that view (Data Access). But when i check it from child site console in that view there is child site admin logins and "greyed" views without capability to change anything in packet settings....Is any ideas, misters....
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2013 5:17pm

Once again, by design. As mentioned, child site admins only control the deployment of the content, not the content itself or any of its settings.
July 1st, 2013 6:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics