• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows Server 2012 with vCenter Server 5.5

KapsZ28

2[H]4U
Joined
May 29, 2009
Messages
2,114
From what I am reading, 2012 R2 is not supported. Is it worth using 2012 or just using 2008 R2? I am doing another vCloud Director environment and will be using all the latest versions of Heartbeat, vCenter, vCloud Director, etc.

What Windows and SQL versions would you use?
 
Yeah I ran into the 2012 R2 incompatibility this weekend :( Should have read the matrix. It hangs at a certain point of the install. 2012 works just fine so I went with that.
 
Maybe I am missing it, but I don't see anything about SQL. I'm guessing SQL Server 2012 SP1 is fine for everything?
 
You know what I haven't been able to find. What features need to be installed on a SQL instance for vCenter, Update Manager, etc. I want to install just the required features. Drives me nuts when someone installs All features.
 
I only install the client tools and the actual database functions. Everything else I just leave out. Haven't had an issue.
 
I only install the client tools and the actual database functions. Everything else I just leave out. Haven't had an issue.

Awesome, thanks! Do you use one instance with multiple DBs or install separate instances?
 
I just pointed my vCenter at our regular SQL DB the last time I built a 5.x setup. The current one here is a 4.1 with a local SQL install but I'm waiting on hardware to change that.
 
I see that Windows Server 2012 R2 is now on the compatibility list. At least for 5.5 U1. Has anyone used it yet? I would much rather use R2 than the non-R2.
 
Ok now i have problem with DHCP data base

C:\Users\Administrator\Desktop\dhcp - Copy>net start dhcpserver
The DHCP Server service is starting.
The DHCP Server service could not be started.

A service specific error occurred: 20013.

More help is available by typing NET HELPMSG 3547.


C:\Users\Administrator\Desktop\dhcp - Copy>

I have tried jetpack

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>net start dhcpserver
The DHCP Server service is starting.
The DHCP Server service could not be started.

A service specific error occurred: 20013.

More help is available by typing NET HELPMSG 3547.


C:\Users\Administrator>net helpmsg 3547

A service specific error occurred: ***.



C:\Users\Administrator>jetpack.exe
usage: jetpack.exe [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

C:\Users\Administrator>cd c:/

c:\>cd Windows

c:\Windows>cd System%debug
The system cannot find the path specified.

c:\Windows>cd System

c:\Windows\System>cd dhcp
The system cannot find the path specified.

c:\Windows\System>cd../

c:\Windows>cd System32

c:\Windows\System32>cd dhcp

c:\Windows\System32\dhcp>jetpack.exe
usage: jetpack.exe [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

c:\Windows\System32\dhcp>jetpack.exe
usage: jetpack.exe [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

c:\Windows\System32\dhcp>net stop dhcpserver
The DHCP Server service is not started.

More help is available by typing NET HELPMSG 3521.


c:\Windows\System32\dhcp>jetpack
usage: jetpack [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

c:\Windows\System32\dhcp>jetpack dhcp.mdb dhcp-tmp.mdb
jetpack failed with error = -550

c:\Windows\System32\dhcp>jetpack dhcp.mdb tmp.mdb
jetpack failed with error = -550

c:\Windows\System32\dhcp>jetpack dhcp.mdb
usage: jetpack [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

c:\Windows\System32\dhcp>jetpack dhcp.mdb tmp.mdb
jetpack failed with error = -550

c:\Windows\System32\dhcp>jetpack dhcp.mdb tmp.mdb
jetpack failed with error = -550

c:\Windows\System32\dhcp>jetpack.exe dhcp.mdb tmp.mdb
jetpack.exe failed with error = -550

c:\Windows\System32\dhcp>jetpack.exe
usage: jetpack.exe [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

c:\Windows\System32\dhcp>jetpack.exe dhcp.mdb tmp.edb
jetpack.exe failed with error = -550

c:\Windows\System32\dhcp>jetpack.exe /?
usage: jetpack.exe [-351db] <database name> <temp database name>
: Use -351db if you are compacting NTS3.51 or prior release database
: Use -40db if you are compacting NTS4.0 release database
: Default - compacts NTS5.0 release database

c:\Windows\System32\dhcp>JETPACK DHCP.MDB TMP.MDB
JETPACK failed with error = -550

and now ...

c:\Windows\System32\dhcp>JETPACK DHCP.MDB TMP.MDB
JETPACK failed with error = -1209

c:\Windows\System32\dhcp>

550 Database is in inconsistent state

1209 i cant find ...

any advice ?
 
I actually just loaded up my first 2012 R2 VM last week on 5.5 U1. No problems, at least related to vSphere. It's a SQL Server that is also running some Cognos tools. Most my problems have been changes related to OS or UI that I'm just not use to yet. Think I've got everything ironed out now and once I get my DCOM stuff hammered straight we should be good. I'm by no means an expert but I think we'll be going straight 2012 R2 now.
 
I actually just loaded up my first 2012 R2 VM last week on 5.5 U1. No problems, at least related to vSphere. It's a SQL Server that is also running some Cognos tools. Most my problems have been changes related to OS or UI that I'm just not use to yet. Think I've got everything ironed out now and once I get my DCOM stuff hammered straight we should be good. I'm by no means an expert but I think we'll be going straight 2012 R2 now.

I've been using 2012 R2 as a VM for awhile. I am referring to using 2012 R2 as the guest OS for installing vCenter Server. Previously it was not supported and people had reported issues. Just hoping that is not the case now.
 
I've installed and upgraded vCenter 5.5 and 5.5u1 on both 2012 and 2012 R2 without major issues now. Zero issues with U1 and 2012 R2 now. It works fine :)
 
Last edited:
Having hanging issues on 2012 r2. I am just setting it on top of 2008 r2. Meh.
 
SQL embedded or external?
You add the necessary roles and do all of the prep work first?
Oh this is u1 right?
 
Having hanging issues on 2012 r2. I am just setting it on top of 2008 r2. Meh.

You did a Server 2008 R2 upgrade to Server 2012 R2? I've done a bunch of upgrades like this for different roles, and did have an issue with one server. It kept freezing and had to be hard booted. I ended up doing a clean install of 2012 R2 and the issue went away.
 
You did a Server 2008 R2 upgrade to Server 2012 R2? I've done a bunch of upgrades like this for different roles, and did have an issue with one server. It kept freezing and had to be hard booted. I ended up doing a clean install of 2012 R2 and the issue went away.

Oh dear lord no. I haven't done an inplace upgrade since 2000-2003. 9/10 times it is easier and less problematic to just move your services and applications to a new host. This is just a fresh build for testing. Our current env is 4.1, so am looking into 5.5 to see if it would be worthwhile for us to upgrade yet.
 
Wait, my production Windows 2012 R2, SQL 2012 server I've been constantly upgrading since it was SQL 2000 running on Windows NT isn't a good idea? WTF?????
 
Wait, my production Windows 2012 R2, SQL 2012 server I've been constantly upgrading since it was SQL 2000 running on Windows NT isn't a good idea? WTF?????

If by some act of the diety of your choice you managed to pull that off, sir, I'd salute you.
 
Windows 2012 R2 is supported with vSphere 5.5 U1 or vSphere 5.1 U2 Any other versions had issues with installing... I just setup my vCenter on Windows Server 2012 R2 no issues!

However these are fresh builds i never do the Upgrade unless its like a Domain Controller and its absolutely necessary!
 
Windows 2012 R2 is supported with vSphere 5.5 U1 or vSphere 5.1 U2 Any other versions had issues with installing... I just setup my vCenter on Windows Server 2012 R2 no issues!

However these are fresh builds i never do the Upgrade unless its like a Domain Controller and its absolutely necessary!

Waste of time to upgrade a DC, just bring a new one online and move over master roles if you need to. The last windows upgrade I did was 2000 server to 2003 server mainly because AD wasn't as robust as it is now and we were limited by physical hardware to 2 DC's. Now I have dozens of hosts spread around. It will take a serious disaster to kill my domain.

Oh and that NT server upgraded from NT to 2012r2 isn't really upgraded. Since 2008 it has been swap image and migrate data/settings. The upgrading as it used to exist stopped at 2003. *semantics* lol :D

I do know a dumbass that made the dire mistake of upgrading an NT 4.0 domain server to 2003... Fucking BAD. lol. Broken wasn't even the word for it. He never jumped into an upgrade again. (looks at self, hangs head in shame.) Thankfully it was such a small environment it was fixed after a very long night. Nobody even noticed.
 
I only mentioned the upgrade with the DC due to a bug i hit in 2k3 that wouldnt let me migrate the Roles, it was locked down, the upgrade (2008) fixed whatever it was (MS recommendation) and i was able then to transfer the roles into a new box and down the old.
 
I only mentioned the upgrade with the DC due to a bug i hit in 2k3 that wouldnt let me migrate the Roles, it was locked down, the upgrade (2008) fixed whatever it was (MS recommendation) and i was able then to transfer the roles into a new box and down the old.

No I understand. There are always exceptions. My general rule is turn up a new one and transfer, but no, sometimes that is not an option.
 
Back
Top