jrlane

This is driving me mad. Still no solution. Ideas?

I have an OSD task sequence that deploys an OS then installs 9 applications. If i deploy the TS the machines will get the task and show downloading 0% in the software center. Looking at the logs (execmgr i believe) i can see that it is waiting on a depency, however it does not tell me what the depency is! It only tells me that it's something to do with the OSD task sequence package. Keep in mind that looking at the references tab for the TS it shows all of the references are 100% compliant for all of our DPs. If i disable the 9 application installs in the TS, it runs beautifully as expected. This has happend to us in the past and last time I had thought it had something to do with one of the applications having a supercedence relationship with a retired package that was never distributed. I have checked for this again and didnt find anything (im going to check once more to make sure). Does anyone have any tips on how i can definitively track down what is causing this?

I'm looking for some suggestions on ways i could create an application that requires the use of a database file hosted on each of our locations fileserver. Our setup is pretty basic: Primary site server that is also a DP and 8 other DP sites. Every DP (including primary) has a fileserver with a database file that is used by a keyboarding application that is specific to each site. For example: Site A: DP - aDP.local Fileserver - aFP.local Site B: DP - bDP.local Fileserver - bFP.local FYI depending on the site, sometimes the DP is the same server as the fileserver. So basically what i need is, somehow the script that installs the application needs to be away of what DP the device its installing it on belongs to and make the right database file location association.

Required

Yes, i have waited 2 hours over lunch, and i have also tried forcing policy refresh on both the sccm console and the machine itself from the control panel.

I'm a little fuzzy on the functionality of OSD deoployments. We have a working image with a task sequence that has been deployed to a collection. Along with the task sequence we have a number of standard applications that have been deployed to that collection. When I restart the machines after setting the deoployment, the machines image perfectly; the image gets pushed, and after the first boot, the deoployed applications get pushed as well. My confussion is how is this supposed to work hands off. Everything I have tried does not restart the machines in the collection; i have to manually reboot the machines for the PXE boot to start. I have tried different combinations of (PXE, client, media; PXE, client (hidden)...) none of which restart the machine. I have also tried manually updating policies and such. Lastly, what is the proper way to "re-image" a machine? Would it be to remove the deoployment and re-add it, deploy ontop of the existing, or clear the PXE flag?