rich0dify

Hi, I'm having a bit of a lapse in brain function - I had a secondary site server go down and am in the process of rebuilding it, I've got it all up - everything appears to be fine, but SCCM hasn't created any folders in the DP drive.. I've tried pushing stuff to it, but nothing appears to go through, and it's been quite a while since I've had to do anything with SCCM in the way of diagnosing package issues as it's been up and running flawlessly for 2 years+. But the check list of things which have been done, WebDAV configuration AD schema permissions Key exchange Ensuring machine accounts are in local admin\SCCM created groups NO_SMS_ON_DRIVE.SMS is only present on C: Firewall off Numerous reboots Multiple package push attempts System info: Win2k8 R2 - SCCM 2007 R3 - SQL 2008 R2, both pri\sec are VMs. But still I can't either remember where the specific log files are I have to trawl through that pertain to package pushing, or what I did before to look into this as I'm *pretty* sure I had this before when initially setting it all up, but can't for the life of me remember what it is. Any ideas as to where to look I'd be very grateful. Thanks

I've got CM07 to do updates for workstations, which are approved\deployed by us from our own managed CM\WSUS server setup, but we have another WSUS server which is a downstream for pre-approved updates for servers from our corperate office, I was hoping that I could have CM look at this downstream server *as well as* our own managed WSUS server to apply patches via CM? Could I possibly get it to point to the WSUS content location of the corp approved WSUS server when creating a deployment package? Or have a seperate instance of SU on a secondary site which looks to the *other* WSUS server? I'd like to exhaust all possible routes to get my server patching at an easier level, just having to log on to 120+ servers and click the shield is a mightly boring way to spend my Saturday once a month!

Hi there, I was wondering if there was a way to get the above scenario working as our workstation patch management is managed by us, but server patch management is pre-approved by our parent company... Ideas? Thanks -Rich