VC works fine with SQL 2012 if you're on 5.5.
But anyway, blame the software vendor. If their software requires a VC redist package then it should be included with the software, treated as a prerequisite and automatically installed before their software is so that when you are done it works.
Oh sure, it did - after updating the SQL server to SP1, installing two SQL packages on the VC, renaming the local admin account on the VC...and then having the web client shit itself and require a reinstall (with VMware saying it's a "known issue with no fix"), lol.
One of the more non-intuitive installs I've done, anyway.
Uh, really? And how am I supposed to know what will and what will not fuck up Windows? Purveyors of software do not include a warning that installing their software is apt to trash your OS. It's on the OS developers to protect system files and incorporate internal repair mechanisms. I have to think that this certainly should apply to Windows Updates, which I am absolutely unable to do on this machine, and it's been well over a year since I could. The only strategies I can think of are occasional if not frequent backups of the entire system, before things get so fucked up that it's a lost cause. In the case of this machine the OS appears to be beyond repair. If there is a repair scenario, I haven't found it, and I did look. You can say I fucked up, but you have no evidence that it wasn't Microsoft that fucked up, not me.
1) MS incorporated UAC to allow you to know when software is accessing and/or modifying system files. Many people consider this a nuisance and turn it off or lower it. Same goes for the internet zones & Java. Safeguards exist, people choose to disable them.
2) There are internal repair mechanisms in place, but they can be shut down or disabled by OEMs. I've seen system restore disabled by Dell, and a lot of SSD utilities will disable them to give you max space.
A good Windows software installer will check for prerequisite libraries like .NET runtime and Direct X and download/install them FOR you.
Easier Tham doing yum updates.
Literally all software installers require administrator access. This completely disregards the original complaint.
So instead of preventing a system failure, the best solution is to delete everything and restore from a backup. That's another problem.
Uh....SQL 2012 doesn't require SP1 according to our interop matrix. You may have needed to install version 11 of the SQL Native Client Driver on the 2008 box.
Want to PM me the case number? I'll look into it.
Installing the Web Client on drives other than the C drive or in non-default locations sometimes does cause issues. Sometimes it doesn't. I can PM you some other things...
IIRC the SQL server required SP1 (brain is fuzzy now, either was necessary during install or I ended up with an error that Google told me needed SP1, either way), not the vCenter server. The web client was in the default location on the C:\ drive and worked fine for a bit, then decided not to play anymore.
I did need the v11 SQL native client driver, yes.
SQL shouldn't need SP1...or our matrix is wrong. But I'm pretty sure I had a 2012 vanilla in my lab working fine.
Server 2008 R2 (no SP) with SQL 2012?
I may have f'd it up. I dunno.![]()
Yup.
But then...it wouldn't be the first time I've seen a configuration work in one place and not another. And GPO's do strange things.
Says pretty clear on MSDN that Windows Server 2008 R2 SP1 is required. Might be time to update y'alls matrix.
http://msdn.microsoft.com/en-us/library/ms143506.aspx#pmosr
Of course admin access is required to install software - that'd be as stupid of a concept to not require it as your posts are. You shouldn't have admin rights if you don't know what you're doing. Get a Mac and drag-n-drop the idiot proof way.
Also, to your second comment - that is hardware vendors that disable stuff, not Microsoft. Don't knock them for that bullshit.
Ding ding ding! Winner.
You install a new program and you can't run it because of a cryptic error message. Turns out you need Visual C++ runtime libraries. Isn't that made by Microsoft? Why wouldn't they just include it with the OS?
Okay, let's hunt for that installer. Do I need 2008, 2010, 2012, or 2013? Because they're all completely different and not included in the same installer. No, that would make too much sense. Do you need 64-bit or 32-bit? Because they're also different, incompatible, and not included in the same archive or with the OS.
Oops, I downloaded the update for Visual Studio, not the runtime libraries. Let's go back to that website and hunt through a list longer than my arm. What's SP1? No, I do not want to install the Bing Bar, asshole.
Of course they couldn't just include it with Windows Update. That would be too convenient.
And Windows Update. Man, this piece of crap. You have to run it, download, install, restart, run it, download, install, restart, run it, download, install, restart. Repeat this 20 more times and just maybe you'll have all the necessary updates. Maybe.
Literally all software installers require administrator access.
I may have misunderstood what jlee was talking about - I was assuming that the SQL was on a separate server vs. the vCenter which is a pretty common practice if one is installing a full-fledged SQL and not Express.
In this case, the OS that vCenter is installed on shouldn't matter assuming it is a supported OS and has the proper driver installed to communicate with SQL 2012.
I think you're just an attention seeker.
Stop being retarded, you retard. The game isn't the software with a distribution problem.
Care to address the pirating accusation directly?
Is the copy you're installing 100% legit and in the format/package the publisher released?