Also forces users to install the fixes in a faster timeline than they may be 
comfortable with.
If I don't get a good test in prior to the 14 days then I won't be able to help 
MS with fixing a potentially bad code release.
It is limiting to both parties.
Some of us have to work the job and run the patch management.
It's not going to help anyone.

From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On 
Behalf Of Andreas Hammarskjöld
Sent: Wednesday, April 20, 2016 8:35 AM
To: ms...@lists.myitforum.com
Subject: RE: [mssms] Blogs - No Comments After 14 Days

Good way to limit the 4month of banter calling MS names (rightfully so) after 
they couldn't release a hotfix with the 1511 ADK failure... this way our voices 
won't be heard.

//Andreas

From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Rod Trent
Sent: den 20 april 2016 14:22
To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>
Subject: RE: [mssms] Blogs - No Comments After 14 Days

I agree with it. These are blogs, not troubleshooting mechanisms or officially 
monitored support areas.

From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> 
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Wednesday, April 20, 2016 7:45 AM
To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com>
Subject: [mssms] Blogs - No Comments After 14 Days

How do people feel about this new direction?  Blogs can now only be commented 
on for 14 days after they are released.

·         
https://blogs.technet.microsoft.com/configmgrteam/2016/04/14/an-update-to-our-blog-comments-policy-and-where-to-go-for-assistance-and-support/

I really don't get MS new direction of not putting details into patches and now 
you can only comment for 14 after blogs being released.

Rob







This e-mail and any files transmitted with it are property of Indiana Members 
Credit Union, are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.

Please consider the environment before printing this email.



Reply via email to