#Microsoft windows server 2008 r2 64 bit keygen#
You can disable WoW64 on Server Core with this command:ĭism /online /disable-feature /featurename:ServerCore-WoW64Īfter the server has rebooted, run this command to make sure WoW64 is really disabled:
Member servers, however, don't require WoW64. Thus, if your Server Core machine is a domain controller, you can't disable WoW64. To my knowledge, the only important server roles that require WoW64 are the Active Directory and Active Directory Lightweight Directory Services roles. Most of them are only needed by 32-bit applications. Please note that some server roles and features require WoW64. To check whether you have 32-bit applications on your Server Core machine, you can start the Task Manager (press CTRL+ALT+DEL) and check if there are any processes with "*32" behind the process name. Hence, if security matters on your servers and you are sure that you don't need any 32-bit applications, you should disable WoW64. The main reason why you should disable WoW64 on Server Core is that it reduces the attack surface significantly, simply because most of the malware and hacker tools are 32-bit. I plan to write about this in a later post. You can only save disk space by completely removing the WoW64 package. However, when I uninstalled 32-bit support on Server Core, I didn't notice any significant change on the available disk space or RAM. Some sites recommend disabling WoW64 because this would result in a smaller footprint. However, the fact that Microsoft originally planned to leave out WoW64 in default Server Core installations shows that it makes sense to uninstall it if you don't need 32-bit applications. Microsoft changed this after the beta phase because it turned out that many setup programs for 64-bit server applications are 32-bit. In the Server 2008 R2 Server Core beta, WoW64 wasn't running by default. On Server Core, WoW64 can be uninstalled. However, there is a difference between Server Core and the other Windows Server 2008 R2 editions.
0 kommentar(er)
