regan

thanks, ive tried the following and restarted the wsus service and sccm/wsus server with the same result, it refuses to create a cert. Haven't got much knowledge when it comes to creating a cert to tell you the truth HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup\ Create DWORD value: EnableSelfSignedCertificates = 1

Ive managed to add WSUS to my sccm configuration and push out updates but im trying to now add SCUP and i am unable to create a certificate which i believe is a change to WSUS 4.0? if WSUS automatically creates its own cert can i not just find and use that?

Great guide, can i ask what are the advantages of using SCCM to manage over day WSUS console? My biggest issue is it seems to be a longer process and the lack of removal of superseded updates

thank you, also will i need to remove any registry files or will my new SCCM deployment override anything left behind?

Im trying to work out how to remove old clients and configs from a SCCM server which we have now removed, I've decided the easiest option is to start over but before i do this i would assume i need to remove any trace of the old one on client machines, so looking for a Group policy command to do so? Is that the best way forward?

Do i need to manually create a new client in order to update or would this have been done during the SP1-R2 update ?

it hasn't , assume it wouldn't if the SMS_DP$ folder is missing? It seems some packages distribute to the DP and some dont. also ive tried to run the windowsupdateagent manually and it says its corrupt ( i found this in my old configuration manager client package location) Shouldnt there be a new location where the new client has been created?

Since upgrading from 2012-SP1-R2 i haven't been able to upgrade the clients, im fairly sure now after a fair amount of research this is down to the distribution point. I would assume that if there was an issue with the distribution point the update wouldn't be sent to the clients. Im fairly sure i have the automatic updated all done, via the Hierarchy settings. Its only when i went to distribute content on one of my packages i realised that the issue might be with the MP/DP as i get "failed to distribute content details will be available after server finishes processing" In distmgr.log i get "package sitename00002 does not have a preferred sender. Used 0 out of 3 allow processing threads In smsdpmon.log There is nothing for months which was my next check. I have Noticed that there inst a SMS_DP$ folder but i do have a inetpub folder ( IIS ) Tried removing and Adding the DP which had no effect. Is there any other logs which might give me an error code 3 to try and work out what the issue is?

I ran the machine policy retrieval and evaluation cycle manually on a client machine, which log should i look at to show recent requests ?

Hi this is my first post, i have been using the guides on the site for a while and to be honest this is the first problem i have been stuck with. I have updated from SP1 to R2 and all seems fine, i have since changed Hierarchy Settings to update client automatically within 2 days. Its now been 2 days and there is no sign of any clients being updated. All clients say inactive and don't seem to have any activity via heartbeat since the upgrade to R2 but do show recent logons so there is some kind of communication's.