We had full day informal training yesterday with Microsoft in our County. During the Server 2012 R2 session, someone asked if there were any changes in WSUS for R2. ‘Nope!’, they told us.
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Mott Sent: Thursday, October 24, 2013 10:53 AM To: [email protected] Subject: RE: [mssms] Scup issue That’s is soooo stupid. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, October 24, 2013 1:41 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Scup issue You’ll love this… According to the WSUS Product Team, WSUS no longer issues self-signed certificates<http://blogs.technet.com/b/wsus/archive/2013/08/15/wsus-no-longer-issues-self-signed-certificates.aspx> as of R2. The link does include a reg hack to re-enable, but the API is deprecated and will likely disappear in the future. The supported solution is to install Windows Server Certificate Services and issue the cert that way. -Phil _________________________________________________________________ Phil Schwan | Technical Specialist, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Wednesday, October 23, 2013 8:06 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Scup issue Other thought... your config file. http://myitforum.com/cs2/blogs/rzander/archive/2011/05/30/scup-2011-with-shared-database.aspx The db maybe was pointing somewhere else the first times you ran it, or your profile was wiped? So the db was lost too? Roland Janus <[email protected]<mailto:[email protected]>> wrote: Tried that already. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Mittwoch, 23. Oktober 2013 23:55 To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Scup issue UAC Right-click Run as administrator I've just made a shortcut on my desktop with the run-as-admin set up on the shortcut. I've been burned too many times by the SCUP console when I forget to run as admin. Sherry Kissinger Microsoft MVP - ConfigMgr [email protected]<mailto:[email protected]> ________________________________ From: Roland Janus <[email protected]<mailto:[email protected]>> To: [email protected]<mailto:[email protected]> Sent: Wednesday, October 23, 2013 4:17 PM Subject: [mssms] Scup issue New install of CM12SP1R2 and SCUP on Server 2012R2. I never had this combination, but somehow I doubt that is the reason for this: The screen looks like that, always, [cid:[email protected]] This is the message I get when clicking either Test or Create, any combination on how to connect the WSUS makes no difference and it never changes or even creates a cert. [cid:[email protected]] The SCUP log in %temp% says: The system cannot find the file specified That’s all, no other error us other indication. Any ideas? The system cannot find the file specified [cid:[email protected]] [cid:[email protected]] Roland Janus IMS Informatics AG Providing Services to Novartis Pharma AG Lead Architect SCCM 2012 Project Phone number : + 41 61 32 43902 e-mail: [email protected]<mailto:[email protected]> ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments. ________________________________ DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of this email address. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ________________________________ CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
