It is much less painful to reinstall a lab with System Center now, or just reinstalling Configuration Manager with PDT. I can reinstall a home lab environment in less than 3 hours, and if you only need ConfigMgr, it will do it in about an hour on a relatively low powered home lab server or "lab"top...
http://www.systemcentercentral.com/my-2nd-week-with-the-powershell-deployment-toolkit-pdt/ Combined with other methods for restoring your customizations, you should not have a problem with using the 180 day eval software From: [email protected] [mailto:[email protected]] On Behalf Of Michael Mott Sent: Monday, July 01, 2013 9:23 PM To: [email protected] Subject: RE: [mssms] OT: Microsoft to shut down TechNet subscription service +1 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Monday, July 01, 2013 10:20 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OT: Microsoft to shut down TechNet subscription service 180 days is ridiculous, and it requires me to constantly be connected to even access the systems! It just so happens that some of my customers have either: 1) terrible guest wireless connectivity, or 2) no guest wireless connectivity. I'm guessing most other people can relate to that. So now what? Are you going to tell me to use my mobile phone to tether? That would be: 1) ridiculously slow, and 2) my coverage isn't good enough to guarantee that I can always use this, and 3) this doesn't work on a plane. So right, I'm supposed to pay for, and use, the airline's in-flight wifi? Laughable. It costs a hell of a lot, it's ridiculously slow, and it's not available on a huge percentage of flights! On top of all that, the "virtual labs" don't give me enough flexibility to test out all of the scenarios that I need to! Let's say that I'm having a problem with a customer's deployment package, and I need to test out that deployment package through my local ConfigMgr 2012 lab (after taking a snapshot, of course, so I can roll it all back)? How am I supposed to do that with a "virtual lab?" How do I test out PXE booting in a "virtual lab?" How do I test out pre-staged media in a "virtual lab?" How do I test out device driver packages in a "virtual lab?" How do I test out booting from a USB flash drive in a "virtual lab?" Will they give me enough VMs, and access to all the installation media necessary so that I can install a SQL Server / ConfigMgr 2012 database replica, and five Management Points for load balancing? Will they give me access to Windows 8 retail media so that I can develop task sequences? Do I get a choice of which operating system I have my virtual lab running on, or am I always stuck with the latest operating system (not necessarily a bad thing, but it's also not practical / real-world). Bottom line: Retirement of TechNet subscriptions right now is way too premature. Ridiculous. Insane. Cheers, Trevor Sullivan [WordPress Logo 32px]<http://trevorsullivan.net/> [Twitter Logo 32px] <http://twitter.com/pcgeek86> [Facebook Logo 32px] <http://facebook.com/trevor.sullivan> [Google+ Icon 32px] <https://plus.google.com/106658223083457664096> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Monday, July 1, 2013 3:08 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OT: Microsoft to shut down TechNet subscription service I think the intent is for ITPros to use the 180 day evals for their own labs. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rod Trent Sent: Monday, July 1, 2013 3:02 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OT: Microsoft to shut down TechNet subscription service There's also the virtual labs. You no longer have to maintain special hardware. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, July 01, 2013 3:22 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OT: Microsoft to shut down TechNet subscription service Spinning up an Azure VM does not meet the requirement of MSDN software. I can't test on my hardware, in my data center, in my environment without MSDN or paying for software. Microsoft is going to push this Azure crap too hard and people are simply going to stop using MS software. People are heavily invested in the Microsoft skillset but other than the bodies running the systems there's no other real dependency upon Microsoft. We could just as easily run on open source. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rod Trent Sent: Monday, July 01, 2013 2:12 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OT: Microsoft to shut down TechNet subscription service Not really, when you think about it. TechNet was used more for downloading software than any of the other benefits. You can spin-up a Windows Azure VM and test the same software now. No reason to have it on-premise for testing. Plus, the other options they are offering as replacements are all free. They are keeping MSDN, though (for a while), so you can subscribe to that if you want to download bits. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Spinelli, Robert J Sent: Monday, July 01, 2013 2:37 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] OT: Microsoft to shut down TechNet subscription service This is pretty terrible, TechNet yearly subscription was great. http://www.zdnet.com/microsoft-to-shut-down-technet-subscription-service-7000017541/ Thank you. Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | [email protected]<mailto:[email protected]> This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ 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.
<<inline: image001.gif>>
<<inline: image002.gif>>
<<inline: image003.gif>>
<<inline: image004.gif>>
