I've worked for lots of big companies, made my voice heard for years on how bad the restore process and HA is in the product. They did throw us a bone and allowed you to restore the database to a server with a different name, but the hard coding of servers names still being in the product after all these years is a joke.
SQL AlwaysOn still not being supported is insane. Whenever I go to a company and tell them here is the restore process, they look at me like I'm insane. They all say this can't be correct. Gives SCCM a really big black eye for any new company looking to adopt it. From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, May 29, 2015 9:47 AM To: [email protected] Subject: RE: [mssms] SCCM 2016 TP2 - Questions Being an early beta, a lot of things just aren't there yet, don't work, and/or simply haven't been documented so there is no good answer to the below. All of the below have been raised as "concerns" with various members of the product group over the past few years but I have no idea if any of the below are addresses in v.Next or not. Basically, if you want these, file them on connect to make sure your voice gets heard. J From: [email protected] [mailto:[email protected]] On Behalf Of Robert Spinelli Sent: Friday, May 29, 2015 8:37 AM To: mssms Subject: [mssms] SCCM 2016 TP2 - Questions I haven't played with SCCM 2016 TP2, was wondering if anyone knows is it any better when it comes to disaster recovery / HA ? Please don't tell me you still need to have the same server name for CAS/Primary when doing a restore. Does it support SQL AlwaysOn? Any info is appreciated. Thanks Rob
