|
EdwardKK -> RE: Tool to refresh DPs (6/13/2008 2:04:57 PM)
|
Brian, I hadn't thought of that. I had thought that if I set the schedule to update the dps on a regular basis that will update the package number, which would then tell clients that they haven't run the current version of the program. But you're right, I could just refresh them all once a week or so. But I'm not sure it's worth it to do so. I really am looking for more of a one off solution. For example, if I have hardware replaced, and just want to refresh all the packages to make sure its all happy. But it's probably not a bad idea to set these sites to refresh anyway once a week just to be certain they are up to date.
I tried that in CloneDP, and it sort of works. it would just be nice if you could just pick a site system and say "refresh all assigned packages" Brian's right, I'm looking for more of a right click type of command. Does SCCM have this? Anyone know?
Part of the fun is that I have some packages which orginate from the local SMS server, and some originate from the parent site. So CloneDP can work in some instances, but it creates an interesting mesh of locked packages on site systems depending on where I run it from. If i run it from the parent, then I can't manage it's changes from the child in the future, and vice versa. I could get around this by not assigning packages to sites from the parent, but I have to manage other child sites from that parent, so there is no perfect answer for me.
Oh the inhumanity..... woe is me. [:D]
|
|
|
|
