.NET 3.0 and 3.5 in Windows Server 2008 R2 Server Core

コマンド備忘録 (開発者も、Server Core への準備)

松崎剛 Blog — Thu, 09 Apr 2009 15:02:33 GMT

こんにちは。(やはり、ブログに書いておくことにしました . . .) ご存じの通り Server Core は、Windows Server 2008 R2 で .NET 開発者にとっても無関係なものではなくなりました。いままでは

re: .NET 3.0 and 3.5 in Windows Server 2008 R2 Server Core

maweeras[MSFT] — Fri, 03 Apr 2009 13:26:17 GMT

Andrew

It appears that a reboot is required after the "start /w ocsetup ServerCore-WOW64" command. There was no prompt in the console indicating this was required and the c:\windows\logs\cbs\cbs.log was 0 bytes in size. I ran the command multiple times to no avail. "oclist | findstr /i wow" showed NOT installed. But during shutdown portion of the reboot I could see some updates were done (as per status messages) and after reboot cbs.log was a little over 1MB and oclist showed WOW64 support as installed.

Perhaps consider updating the blog entry so that others that dont read the comments dont waste time.

re: .NET 3.0 and 3.5 in Windows Server 2008 R2 Server Core

trent.nelson — Sun, 18 Jan 2009 18:21:46 GMT

Now that .NET is available in R2, does that mean ServerManagerCmd.exe will also be available?

Or, if it's not, is Routing & Remote Access Services a supported role on R2? The inability to set up site-to-site VPNs between Server Core machines is extremely frustrating.