Windows Server 2012 R2 NIC Teaming and DHCP Issue

Came across a weird issue today during a server deployment. I was doing a physical server deployment and got Windows installed and was getting ready to connect it to our network. Before connecting the Ethernet cables to the network adapters, I created a
NIC Team using Windows Server 2012 R2 built-in software with a static IP address (we'll say its 192.168.1.56). Once I plugged in the Ethernet cables, I got network access but was unable to join our domain. At this time, I deleted the NIC team and the two network
adapters got their own IP addresses issued from DHCP (192.168.1.57 and 192.168.1.58) and at this point I was able to join our domain. I recreated the NIC team and set a new static IP (192.168.1.57) and everything was working great as intended.
My issue is when I went into DHCP I noticed a random entry that was using the IP address I used for the first NIC teaming attempt (192.168.1.56), before I joined it to the domain. I call this a random entry because it is using the last 8 characters of the
MAC address as the hostname instead of the servers hostname.
It seems when I deleted the first NIC team I created (192.168.1.56), a random MAC address Server 2012 R2 generated for the team has remained embedded in the system. The IP address is still pingable even though an ipconfig /all shows the current NIC team
with the IP 192.168.1.57. There is no IP address of 192.168.1.56 configured on the current server and I have static IPs set yet it is still pingable and registering with DHCP.
I know this is slightly confusing but I am hoping someone else has encountered this issue and may be able to tell me how to fix this. Simply deleting the DHCP entry does not do the trick, it comes back.

Hi,
Please confirm you have choose the right NIC team type, If you’ve previously configured NIC teaming, you’re aware NIC teams usually require the assistance of network-side
protocols. Prior to Windows 2012, using a NIC team on a server also meant enabling protocols like EtherChannel or LACP (also known as 802.1ax or 802.3ad) on network ports.
More information:
NIC teaming configure in Server 2012
http://technet.microsoft.com/en-us/magazine/jj149029.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Windows Server 2012/2012R2 NIC Teaming Mode

Hi,
Question 1:
In Windows Server 2012 the following teaming mode was recommended for Hyper-V NIC teams:
Teaming mode: Switch Independent
Load balancing mode: Hyper-V Port
All Adapers Active
In a session at TechEd 2014 it was stated that Dynamic is the new recommendation for Windows Server 2012 R2. However, a Microsoft PFE stated a few weeks ago that he would still recommend Hyper-V Port for Windows Server 2012 R2. What is your opinions around
this?
Question 2:
We have a Hyper-V Failover Cluster which isn`t migrated to 2012 R2 yet, it`s running 2012. In this cluster we use Switch Independent/Hyper-V Port for the team. We also use converged networking, having 2 physical adapters bound to the NIC team, as well as
3 virtual adapters in the management OS for management, CSV and Live Migration. Recently one of the team NICs failed, and this incident also caused the cluster membership on the affected node to go offline even though the other team NIC was
connected. Is this expected behaviour? Would the behaviour be different if 2012 R2 with Dynamic mode was being used?

Hello,
As for question number 1:
For Hyper-V workload it's recommended to use Dynamic with
Switch Independent mode. Why?
This configuration will distribute the load based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm will redistribute flows to optimize team member bandwidth utilization so individual
flow transmissions may move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets so it takes steps to minimize that possibility.
The receive side, however, will look identical to Hyper-V Port distribution. Each Hyper-V switch port’s traffic, whether bound for a virtual NIC in a VM (vmNIC) or a virtual NIC in the host (vNIC), will see all its inbound traffic arriving on a single
NIC.
This mode is best used for teaming in both native and Hyper-V environments except when:
1) Teaming is being performed in a VM,
2) Switch dependent teaming (e.g., LACP) is required by policy, or
3) Operation of a two-member Active/Standby team is required by policy.
As for question number 2:
The Switch Independent/Hyper-V Port will send packets using all active team members distributing the load based on the Hyper-V switch port number. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port
is affinitized to exactly one team member at any point in time.
In all cases where this configuration was recommended back in Windows Server 2012 the new configuration in 2012 R2, Switch Independent/Dynamic, will provide better performance.
Microsoft recommend for a clustered Hyper-V deployment
in Windows server 2012 to use Switch Independent/Hyper-V Port as you mentioned and to configure
Hyper-V QoS that applies to the virtual switch. (Configure minimum bandwidth in
weight mode instead of in bits per second and Enable and configure QoS
for all virtual network adapters
Did you apply QoS on the Converged vSwitch after you
created the team?? However Nodes are considered down if they do not respond to 5 heartbeats. The Switch Independent/Hyper-V Port does not cause the cluster to goes down if one NIC failed. The issue is somewhere else and not in the teaming mode
that you choose.
Hope this help.
Regards,
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if
a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

2012 R2 NIC Teaming and netwroking

I have a 4 port NIC, all connected to the same network using DHCP, when I team two cards, they no longer have an IP address. Is that by design?
Where can I find more information about the virtual networking how to?
TIA

Yes it is by design.
If individual NICs are configured with IP settings and then you create a NIC teaming the individual nics will lose their IP settings.
And you will no longer be able to configure the ip settings on the individual NICs which are part of a NIC team. Instead you will need to assign the ip address on the NIC Team.
To assign ip address to the NIC teams, go to control Panel\ Network and Internet\ Network Connections
To assign VLANs and manage/update Team interfaces: In the Server Manager select the local server and then in the local server properties section click on Nic Teaming "Enabled" link.
This will open the NIC teaming window and here you can manage the NIC teams.
For more information on NIC teams please refer to:
http://blogs.technet.com/b/keithmayer/archive/2012/11/20/vlan-tricks-with-nic-teaming-in-windows-server-2012.aspx
Kind Regards Tim (Canberra)

Unable to add File Server Resource Manager Tools on Windows Server 2012 - Errors on restart and roll back install

Unable to install Windows Server 2012 Feature - [Tools] File Server Resource Manager Tools.
Installs, however when I restart the server error messages appears saying feature unable to install, windows reverting changes.
In the Setup event logs have the following information message "Update FSRM-Infrastructure of package FSRM-All failed to be turned on. Status: 0x800f0922"
Does anyone have any idea's on why this Feature can not be installed ??
Scott

Hi Shaun
Tried both of your suggestions, however neither strategy worked.
Strategy 1
Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"
Feature un-installed itself during the restart.
Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services". However
this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
PACKAGE SERVICING COMMANDS:
/Add-Package - Adds packages to the image.
/Remove-Package - Removes packages from the image.
/Enable-Feature - Enables a specific feature in the image.
/Disable-Feature - Disables a specific feature in the image.
/Get-Packages - Displays information about all packages in the image.
/Get-PackageInfo - Displays information about a specific package.
/Get-Features - Displays information about all features in a package.
/Get-FeatureInfo - Displays information about a specific feature.
/Cleanup-Image - Performs cleanup and recovery operations on the image.
Strategy 2
Tried installing via powershell, using the following command DISM
/online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
All up back to where I started?

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

Windows server 2012 as primary DC and DNS server and windows server 2003 as secondary DC and DNS

Migration from windows server 2003 AD DC and DNS server to windows server 2012 R2,
Cannot I set up Windows server 2012 R2 as primary DC and DNS , windows server 2003 as secondary DC and DNS ? (for backup server when server 2012 fail, user can continue to login and access internet services)

You can mix both as long as your Forest and Domain Functional level are Windows Server 2003. However, I would like to bring your attention to this blog about known problems when mixing DCs with Windows Server 2003 and 2012 R2 OS:
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Windows Server 2012 - Direct Access clients and the Windows 8 firewall

Hi,
We're running a simple proof-of-concept for Server 2012 Direct Access, we have a single DA server behind a firewall using NAT. We have a number of client devices setup for DA and running Windows 8.
Our issue is that we can only get the Windows 8 direct access clients to connect (when outside the corporate network) and work with the windows firewall disabled (public network profile).
With the windows firewall disabled everything works exactly as expected. When outside the corporate network the client detects the network state (public network profile), connects via DA and all internal resources can be accessed successfully...fantastic.
Is there some specific guidance on manually configuring the windows 8 firewall for Direct Access ? We've tried the obvious TCP:443 with edge traversal enabled but without success.
Much of the information we have found relates to UAG rather than Windows 2012 DA.
Any assistance is appreciated.

Hi,
There isn’t any specific configuration on the firewall.
Just confirm that port 443 can be forwarded to DirectAccess server.
Of course, make sure you are using IPsec first.
Check the links:
STEP 6: Test DirectAccess Client Connectivity from Behind a NAT Device
http://technet.microsoft.com/en-us/library/hh831524.aspx#TeredoCLIENT1
DirectAccess for Windows Server 2012 Installation & Configuration Guide
http://syscomlab.blog.com/2012/09/directaccess-for-windows-server-2012-guide/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WIndows Server 2012 w/ Hyper V and Windows 7

I have been able to create every imaginable virtualization in a test environment except for Windows 7. It asks for drivers. I have a driver CD but when I put the CD in the D: drive. It will run but suddenly the command line screen states that a file on
the F: drive does not exist. Where is this F: drive coming from?

I might have misstated my situation. I have Windows Server 2012 outfitted with Hyper-V. I'm trying to virtualize a Windows 7 operating system.
I found a another W7 media disk that seems to bypass this problem.

Windows Server 2012 Pooled Virtual Desktop collection GetVMstate issue

I am trying to create a Pooled Desktop collection with my Powered off VM and it errors out The
virtual desktop must be in a stopped state: Could not identify the state of the virtual desktop. Ensure that the RD virtualisation host server is available on the network and the virtual desktop is shut down
In the debug logs it shows.
Component RdmsModel: GetVMstate for Vm Win7_BaseVM failed with error 16386
Component RDExceptionHandler: Could not identify the state of the virtual desktop. Ensure that the RD Virtualization Host server sunflower-1.HYPERQA.NUTANIX.COM is available on the network and that the virtual
desktop Win7VMSF is shut down.
Please help on resolving this GetVMState issue.

Hi Krishna,
Thank you for posting in Windows Server Forum.
When you are configuring RDVH initially, please see that you have meet prerequisites. Remember that you need these pre-requirements:
• Database based on SQL Server 2008 R2
• Static IP Address for all Broker
• Round Robin DNS
• All RD Broker must be members of AD Windows Group (es. RDCB Server Group)
• The group must be insert into SQL Server as sysadmin ONLY for the DB creation. After that DB will be created give the db_owner permission only for their DB
More information.
Windows Server 2012 R2: Unable Add New VDI Template
In addition, we need all RD Broker must have the same SQL Native Client as main SQL Server (es. SQL Server 2012 SP1). The Connection Broker server's computer account MUST be a member of the local administrators group on the Virtual Host (RDS Host) machine and
then reboot the server. Finally check the result.
Windows Server 2012 Virtual Desktop Template Issue
Hope it helps!
Thanks.
Dharmesh Solanki

Server 2012 R2 NIC Teams

Hey guys, i was hoping someone could help me understand this. I kind of get how this teaming stuff works, but i want to make sure I'm not doing anything wrong/ not supported.
So for the past few days I've been trying to wrap my head around this stuff. And this is what I have so far.
R720 Dell Server --> 4 Teamed NICs ---> Multiplexor --> vSwitch --> VMs
So the vSwitch is connected to the multiplexor and the VMs are connected to that switch. I figured I'd try to see if i saw any performance differences. As a matter of fact I saw it got worse. Sometimes the VM on the server stays connected, other times it
gets disconnected and wont reconnect
When I do a LAN speed test to another server i get like 9 Mbps vs other servers that are connected strait from a nic to a switch and that switch to a server that gets 800 Mbps +
I did a switch independent with dynamic LB. I did some looking up on all of the settings, but I really dont understand why its so slow.
Also if i were to create vNICs based off that switch for lets say, management, cluster, live migration etc..
So, the NICs are based off that vSwitch and you can do the Qos for those NICs, but I'm confused as to how those NICs are specifically used.
If none of that made sense, i'll be around looking for some more info and i can elaborate if need be.

Hi,
In switch
independent mode, outbound traffic bandwidth could be increased. If you want improve both inbound and outbound bandwidth you could configure a switch dependent
mode. And it is recommended to choose hyper-v switch port as
Traffic distribution algorithms.
For dynamic teaming
most switches require manual administration to enable LACP on the port.
At last, you referred that VM lose connection intermittently. I wonder the VM lose connection with your virtual switch or lose connection with the other servers.
A good blog for you:
NIC teaming on Virtual Machines
http://blog.marcosnogueira.org/nic-teaming-on-virtual-machines/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope this helps.

Windows Server 2012 R2 - RD Gateway and expired passwords

We got tired of script kiddies trying to brute force our old RDP servers, so we thought RD Gateway was a good idea and implemented this on our newest RDS servers.
That worked fine until the first password change. The support phone got hot for some days.
I understand after investigating the issue that expired has been a problem in the 2008/2008R2 version of RD Gateway.
Are expired/change on first logon still a problem in 2012 R2? I fint this strange after seeing all the old complains.
Are there any solution to this problem (other than running Citrix wich manage password change with no problems)?
Jens Tore Fremmegaard ::.::.:: ServerParkering AS

NLA is disabled. This was never a problem when we used 2008 servers.
On our old 2008 (and 2003 before that) terminal servers the users have always had the opportunity to both change expired passwords and "change password on first logon".
After migrating to 2012 none of them work.
We have a script that warns the users prior to password expiry date, but ther's always someone that waits to long. And then they have to call our support techs to get their passwords changed since password change not working on the rds servers.
Off course they could change it through Exchange OWA, but try to tell that to the CEO that's used to only click their RDS shortcut.
Jens Tore Fremmegaard ::.::.:: ServerParkering AS

Restoring Windows Server 2012 w/ADDS and DNS to Hyper-V

So I asked the Below question in the server 2012 general forum but i am sure it is the wrong forum so I though I would ask it here in the hyper-v forum .
So I have one DC in my environment that I would like to upgrade from Windows Server 2012 to Windows Server 2012 r2. I thought before I upgrade the production server I would convert it to a Hyper-V virtual machine and preform the upgrade on a machine that
can be deleted if the upgrade goes horribly wrong. We use Symantec Backup Exec 2014 to backup and restore. So I was able to restore to a virtual machine, the machine powers on, I was unable to open any of the ADDS administration consoles until
I added a Microsoft loop back legacy NIC. To make matters worse when I try to run the in place upgrade from Windows Server 2012 to Windows Server 2012 r2 I receive and error asking me to first run ADPREP /FORESTPREP and /DOMAINPREP. Unfortunately when I run
either one of these commands I receive an error saying that that ADPREP can find the DNS name for the domain or forest. So my question is how do I restore an ADDS server to a virtual machine and bring up all the services so that it functions in the capacity
that the physical machine was functioning but in a closed environment. Thanks for your time and consideration of my inquiry.
Best regards,
Zajac

Hi Zajac,
>>So I have one DC in my environment that I would like to upgrade from Windows Server 2012 to Windows Server 2012 r2. I thought before I upgrade the production server I would convert it to a Hyper-V virtual machine and preform the upgrade on a machine
that can be deleted if the upgrade goes horribly wrong.
If I understand it correctly , you are going to P2V that DC for upgrade test .
I would suggest you to use Disk2VHD to achieve P2V for your DC then test in-place upgrade .
http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Maximum number of processor sockets in Windows Server 2012 Datacenter and Standard

I have found no documentation on the technical number of supported processor sockets supported by Windows Server 2012 for the Standard and Datacenter editions.
Some donation websites like Techsoup claim that Datacenter supports 64 physical processors and Standard 8, but I can find no authoritative confirmation of this and those look like extrapolation from Windows Server 2008 R2.
So what are the maximum supported # of processor sockets, assuming you have licenses for all of them, for Datacenter and Standard? Do they differ by edition?
In addition, is it true that the total # of supported logical processors in a single system is 640 w/o Hyper-V? It was originally reported to be that, but since Hyper-V's number doubled from 160 in the Beta to 320 in the RC and RTM, did this double too?

You might find some of the information you are looking for here -
http://download.microsoft.com/download/2/C/A/2CA38362-37ED-4112-86A8-FDF14D5D4C9B/WS%202012%20Feature%20Comparison_Hyper-V.pdf. I know there is one change that is not reflected there. Recently the maximum number of virtual machines supported
in a cluster was raised to 8,000 instead of the 4,000 reflected in this document.
The maximum number of sockets for Standard would be two because that is the maximum number that the license supports. Standard has never supported 8. Prior to 2012, it supported 4, and then the licensing changed with 2012 so that Standard would
be sold per processor (socket) with a maximum of two. Technically, the binaries are the same for Standard and Datacenter, so you can most likely get it to run with more somehow, but it is not a supported configuration.
The maximum number of sockets for Datacenter would be 64 - that has not changed from 2008. I make this statement based on the fact that Datacenter supports a maximum of 64 virtual CPUs when run as a virtual machine. Virtual machines don't have
the distinction of socket versus hyper-thread versus core. They see what is presented to them as a processor. But, I doubt very much that you will find any off-the-shelf 64 socket systems; most vendors are relying on the core densities instead
of socket density in order to deliver the horsepower. The above referenced document still shows 320 as the maximum number of logical processors, with or without Hyper-V.
tim

Windows deployment services in windows server 2012 : operating system not found

Hello,
In order of learning WDS in Windows Server 2012, I created a simple test environment composed of :
A Domain controler running WS 2K12 and hosting both DHCP and WDS services. (with the option of not listening port 67 checked while installing WDS)
A test computer, with no operating system
I also added a Windows Server 2012 Standard WIM file and added also (located in [DVD]\sources\install.wim), boot file image (located in [DVD]\sources\boot.wim)
But now, when i start the client, it gives the following error:
While i don't find any reliable solution on Internet, Im looking for your help if ever, anyone faced this problem and found a solution for it or not
Thanks in advance!
Lotfi BOUCHERIT

I find it strange that client and server IP are the same. Is there any sort of DHCP relay agent running on your WDS server ?

Clean Installation of Windows Server 2012 R2 cannot access internet

I just installed a clean Windows Server 2012 R2 Data Center and all drivers installed with no issue. I used Ethernet connection to access internet via IE (let say google.com) but failed. Clicked "Fix connection problem" and returned "website
(www.google.com) is online but isn't responding to connections attempts." Therefore, I suspected Windows Firewall (WF) setting. I disabled WF, allow IE in WF, allow port 80 but all did not work in this case. I am able to ping google.com but it just does'n
work in browser (IE, Chrome, Firefox). The same cable connection I tried with Windows 8.1, 7 with no issue. Please advise is there any clue I miss up for Windows 2012 R2 Data Center?
Sean

C:\Users\Administrator>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : WIN-4O28FIG5HD5
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 30-85-A9-94-5B-62
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.13(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, June 6, 2014 11:46:30 PM
Lease Expires . . . . . . . . . . : Saturday, June 7, 2014 11:46:30 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Users\Administrator>nslookup
Default Server: router.asus.com
Address: 192.168.1.1
> google.com
Server: router.asus.com
Address: 192.168.1.1
Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4001:801::1008
123.136.105.20
123.136.105.35
123.136.105.46
123.136.105.59
123.136.105.49
123.136.105.27
123.136.105.57
123.136.105.37
123.136.105.24
123.136.105.31
123.136.105.53
123.136.105.38
123.136.105.48
123.136.105.26
123.136.105.16
123.136.105.42
LAN settings in IE is set to Automatically detect settings, no proxy is selected.
Sean

Windows Server 2012 R2 NIC Teaming and DHCP Issue

Similar Messages

Maybe you are looking for