- Joined
- Aug 14, 2017
- Messages
- 360 (0.13/day)
- Location
- Edge of the Void
System Name | Serious Series - Serious Server (99.99%) |
---|---|
Processor | 4x Intel Xeon E7-8870's |
Motherboard | HP 512843-001/591196-001 (rev 0B) + 588137-B21/591205-001 |
Cooling | HP ProLiant OEM cooling fans(s) + heatsinks |
Memory | 256GB (64x4GB) DDR3-1333 PC3-10600R ECC |
Video Card(s) | AMD FirePro S9300 X2 + nVIDIA GeForce GTX Titan Xp |
Storage | 1x HGST HUSMM8040ASS200 + 4x HP 507127-B21's + 1x WD Blue 3D NAND 500GB + 1x Intel SSDSA2CW600G3 |
Display(s) | Samsung ViewFinity S70A UHD 32" (S32A700) |
Case | HP ProLiant DL580 G7 chassis |
Audio Device(s) | 1x Creative Sound Blaster Audigy Rx |
Power Supply | 4x HP 441830-001/438203-001's (1200W PSU's) |
Mouse | Dell MS819 |
Keyboard | Logitech K845 (Cherry MX Blue) |
VR HMD | N/a |
Software | VMware ESXi 6.5u3 Enterprise Plus (VM: Windows 10 Enterprise LTSC) |
Benchmark Scores | 3DMark won't let me post my scores publicly at this time... |
Okay, I've some project news.
I had to disable the vCenter Server for Windows instance to get the Active Directory instance installed. But I didn't think to change any networking settings on the vCenter Server (embedded - 6.7) instance before disabling it. With the help of a friend, I managed to fix my DNS and get the Active Directory instance working. It was due to some missing NS records. Once I cleaned up the DNS, I was actually able to get a client device joined to the AD. Now I have to figure out how to make Windows clients connect to the VPN before attempting LDAP sign in, since the AD is VPN-locked. Once I figure that out, I will be able to add any devices I want. Also have to see if I can bind vCenter Server for Windows to a single IP address while it's disabled. Otherwise, I'll have to resort to using the relatively cruddy VCSA again - and who knows how that will go in long term. The last time I used it, it started throwing up more warnings and errors than before, which leads me to question the overall longevity and performance of it. Almost tempted to go without vCenter and Virtual Flash because of the trouble. At least I can start focusing on the rest of the project more in the near future...
Without vCenter, how will I be able to add the Precision T7500, as an ESXi host, to my datacentre? For vMotion?
Also have to figure out whether (and if so, how) to destroy the Virtual Flash resource pool or not...
I had to disable the vCenter Server for Windows instance to get the Active Directory instance installed. But I didn't think to change any networking settings on the vCenter Server (embedded - 6.7) instance before disabling it. With the help of a friend, I managed to fix my DNS and get the Active Directory instance working. It was due to some missing NS records. Once I cleaned up the DNS, I was actually able to get a client device joined to the AD. Now I have to figure out how to make Windows clients connect to the VPN before attempting LDAP sign in, since the AD is VPN-locked. Once I figure that out, I will be able to add any devices I want. Also have to see if I can bind vCenter Server for Windows to a single IP address while it's disabled. Otherwise, I'll have to resort to using the relatively cruddy VCSA again - and who knows how that will go in long term. The last time I used it, it started throwing up more warnings and errors than before, which leads me to question the overall longevity and performance of it. Almost tempted to go without vCenter and Virtual Flash because of the trouble. At least I can start focusing on the rest of the project more in the near future...
Without vCenter, how will I be able to add the Precision T7500, as an ESXi host, to my datacentre? For vMotion?
Also have to figure out whether (and if so, how) to destroy the Virtual Flash resource pool or not...
Last edited: