leedesmond’s blog

You can remotely manage a Windows Server 2008 Core machine using Terminal Services client or Remote Desktop Connection on a Windows Server 2003/2008 or Windows Vista machine.

By default, remote access is disabled on Server Core. You can verify this setting and change it as follows:

C:\>cscript C:\Windows\System32\SCregEdit.wsf /AR /v
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

System\CurrentControlSet\Control\Terminal Server fDenyTSConnections
View registry setting.
1

where 1=disabled, 0=enabled

C:\>cscript C:\Windows\System32\SCregEdit.wsf /AR 0
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

Registry has been updated.

C:\>cscript C:\Windows\System32\SCregEdit.wsf /AR /v
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

System\CurrentControlSet\Control\Terminal Server fDenyTSConnections
View registry setting.
0

Even if you do not explicitly connect to Server Core in console mode e.g. mstsc /console, only one live (console) connection is possible at any one time. The resulting interface will be the familiar Server Core command prompt (no surprise there). Type logoff at the command prompt to end the current session.

Technorati tags: Longhorn, Windows Server Core 2008

No Comments »

To check the System event log on a remote Windows Server 2008 Core machine, you must connect via WMI if PowerShell is used:

[PS] C:\> Get-WmiObject -class Win32_NTLogEvent `
-computer Win2k8core -credential adminuser `
| Where { $_.logfile -match “system” } `
| Select * | Sort-Object -desc timewritten

The PowerShell cmdlet equivalent works on a local machine only:

[PS] C:\>Get-EventLog system -newest 5 | Format-List

Alternatively, use Connect to another computer (Server Core) in the Computer Management MMC snap-in from any Windows OS GUI such as Windows Server 2008/2003 or Windows Vista. This effectively allows you to manage most aspects of a Server Core machine remotely with a graphical user interface.

Technorati tags: PowerShell, Longhorn, Windows Server Core 2008

No Comments »

During installation of Windows Server 2008 Core, it is possible to complete setup without specifying the product key. This means that you have up to 30 days from the installation date to test drive the product before it goes into reduced functionality mode, similar to that in Windows Vista.

In both Windows Server 2008 and Windows Vista, Windows Script Host v5.7 is the scripting engine delivered as part of the standard installation, no different from existing Windows version (from Windows 2000 onwards). You can use either the graphical (WScript.exe) or console (CScript.exe) version of WSH, both located at %windir%\System32. Sorry, there is no PowerShell in Windows Server 2008 Core as the .NET Framework is not part of the product i.e. no managed code support. Only native Win32 code applications can run under Server Core.

So how do you find out the grace period left? Both Windows Server 2008 and Windows Vista ship with the Windows Software Licensing Management Tool in the form of a VBScript called slmgr.vbs at %windir%\System32. Pass the -xpr switch to slmgr.vbs as follows:

C:\>cscript C:\Windows\System32\slmgr.vbs -xpr
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

Initial grace period ends 7/20/2007 1:30:42 PM

To activate the product, use the -ato switch as illustrated:

To confirm that product activation is successful, do the following:

C:\>cscript C:\Windows\System32\slmgr.vbs -xpr
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

The machine is permanently activated.

Running slmgr.vbs on its own at the command line will list the available switches and their purposes. Finally, the important thing to remember is that the network interface card must be correctly configured prior to any attempt to carry out automatic Windows Server 2008 Core product activation (DNS functionality and network connectivity to the Internet required). Otherwise your only other options are to activate over the telephone or an in-house Key Management Server (KMS).

Tested on Windows Server 2008 Core Jun 2007 CTP.

Technorati tags: Longhorn, Windows Server Core 2008

2 Comments »

One major change of the Windows Server 2008 Jun CTP (W2k8JunCTP) is the mandatory requirement to supply a strong password prior to login to a typical installation of W2k8JunCTP. This is with the local Administrator account (default blank password but no prompt for user name).

In contrast, this looks different with Windows Server 2008 Core:

You must first click on the big Other User button and specify Administrator and a blank password at the next screen (below) before you are prompted to change the password.

Technorati tags: Longhorn, Windows Server 2008 , Windows Server Core 2008

No Comments »

Mark sure to reserve your Tuesday 3.7.07 and Thursday 5.7.07 nights next week for the monthly Swiss IT Pro User Group’s event taking place in Zurich and Geneva. Topics cover using SQL Server Business Intelligence to build a Database Warehouse and a technical overview of Windows Server 2008 (Longhorn) by yours truly. Details and registration info here. See you there!

Supported by Schweizer IT Professional und TechNet Blog.

No Comments »

VMRCPlus is a new (unsupported) Microsoft graphical tool that is designed to aid you in the management and administration of Virtual Server 2005, including the recently released SP1 (1.1.603.0 EE R2 SP1 with cool new features such as VHDMount; download). Read more about it with download links from the source.

No Comments »

Do you find yourself wanting to get hold of Citrix Presentation Manager for testing and evaluation purposes? With the new Citrix Evaluation Virtual Appliance (EVA), you now gain access to a 30-day trial that is pre-configured and ready-to-go in the VHD format. Requirements include Microsoft Virtual Server 2005 R2 and 2GB of RAM memory on the host operating system.

More information and download at the official site here.

No Comments »

This is one great reference to keep on your bookshelf if you are keen on mastering Exchange Server 2007. I was one of the MCT technical reviewers for the book’s author - Jim McBee - a fellow MCT based out of Honolulu, Hawaii, during the development of this excellent resource. You will see my name sprinkled over parts of the book ;-). Not just Exchange specific stuff but also cool PowerShell tricks (in Exchange Management Shell).

Check it out now and bookmark Jim’s mostly exchange web blog here.

Mastering Microsoft Exchange Server 2007
by Barry Gerber (Author), Jim McBee (Author)

ISBN-10: 0470042893
ISBN-13: 978-0470042892

No Comments »

In a typical Exchange Server 2007 setup, the client access mailbox settings for all users are already enabled for POP3 and IMAP4 besides the classic MAPI. You can check this through the use of the Exchange Management Shell:

[PS] C:\>Get-CASMailbox johnd

Name ActiveSyncEnabled OWAEnabled PopEnabled ImapEnabled MapiEnabled
—- —————– ———- ———- ———– ———–
johnd True True True True True

Individual user POP3 or IMAP4 access can only be enabled or disabled using the Exchange Management Shell (not configurable on Mailbox Features tab of user in Exchange Management Console):

[PS] C:\>Set-CASMailbox -Identity johnd -POPEnabled:$false

To allow this to actually happen, the Microsoft Exchange POP3 and/or IMAP4 service must be installed and explicitly started by hand (change the startup type from manual to automatic if needed). Do not install the POP3 component (and SMTP) that comes with Windows server itself as Exchange 2007 uses its own enhanced version.

Both POP3 and IMAP4 protocols communicate over unencrypted channels therefore it is advisable to setup secured tunnels such as the use of SSL VPN. A digital certificate is installed by default on an Exchange 2007 server using the host name and FQDN of the internal domain. To enable external access, procure a server digital certificate from a trusted commercial root certificate authority and install on the IIS default web site of the Client Access Server that is reachable (internally in an AD site and/or from the Internet). Configuration can be carried out in Exchange Management Console - Server Configuration - Client Access - Outlook Web Access / owa (Default Web Site) - General / Internal and External URL.

Use Get-PopSettings (or Get-IMAPSettings) to find out the settings that are currently configured on the Client Access Server running the POP3 (or IMAP4) service. Look at Set-PopSettings (or Set-IMAPSettings) to make the required changes.

For more information on POP3 (or IMAP4) configuration:

[PS] C:\>Get-Help Get-PopSettings -full
[PS] C:\>Get-Help Set-PopSettings -full

No Comments »

Now that Office Communications Server 2007 has gone release candidate 1 (RC1), it is time to clean up any existing client components on your host OS, including previous versions of Communicator clients or the recent Office Live Meeting Public Beta client.

Ensure that all (MSN) Messenger, Outlook or any dependent applications are cleanly shutdown first. Only then should you begin with the installation proper. Start setup with the Office Communicator client (CommunicatorEval.msi) followed by the Live Meeting console (LMSetup.exe) before ending with the Live Meeting Outlook integration client (LMAddinPack.msi).

Once setup is complete for all 3 applications, start Communicator and/or Outlook and conduct functional tests to verify that they are working correctly.

No Comments »