Antivirus on Windows Server 2012 Core

List of Antivirus products supported on Windows Server 2012 Core

Supported

Not specified (supports Windows 2012, but don’t say anything about Core)

Not supported

Step by step installation of FCS 1.0 on Windows Server 2008 R2 Core

Installing FCS 1.0 standalone on R2 core is not an easy task.

Here are the steps required to get FCS running and updated.

1. Get FCS media.

2. Copy Directory CLIENT\X64

3. Get the latest hotfix for FCS. Current hotfix: Update for Microsoft Forefront Client Security (KB979536)

4. Slipstream the hotfix with RTM package. That is:

4.1. Run 

all-fcsam-kb979536-x64-enu_718720c77c7fc208f618974b9916d991141ad737.exe /extract

4.2. Copy the extracted file mp_ambits.msi to CLIENT\X64

5. Install FCS in standalone mode:

5.1. ClientSetup.exe /NOMOM

5.2. Wait for completion

6. Enable Automatic Updates with sconfig.

7. Opt-in to Microsoft Update… that’s the tricky part..

7.1. Create opt-in.vbs.

Set ServiceManager = CreateObject(“Microsoft.Update.ServiceManager”)
ServiceManager.ClientApplicationID = “My App”

‘add the Microsoft Update Service, GUID
Set NewUpdateService = ServiceManager.AddService2(“7971f918-a847-4430-9279-4a52d1efe18d”,7,””)

5.2. Run cscript.vbs opt-in.vbs

6. Get the first updates with sconfig:
Search for for (A)ll updates or (R)ecommended updates only? a

Searching for all applicable updates…

List of applicable items on the machine:

1> Microsoft Silverlight (KB982926)
2> Definition Update for Microsoft Forefront Client Security – KB977939 (Definit
ion 1.85.837.0)

Select an option:
(A)ll updates, (N)o updates or (S)elect a single update?

7. Reboot.

8. Wait for the next definitions update.

References:

Opt-in to Microsoft Update via script: http://msdn.microsoft.com/en-us/library/aa826676(VS.85).aspx

Slipstream FCS: http://www.itgeek.co.nz/post/Patch-or-slipstream-Microsoft-Forefront-Client-Security.aspx

Simple iSCSI Lab with Linux & Windows Server 2008 Core

This is a very simple lab scenario for testing iSCSI.
In Linux iSCSI is setup in the usual way: from command line. Since Windows 2008 Core dosen’t have an interface to setup iSCSI initiator, you have to use the linux-way: command line.

iSCSI Target: Linux Box, openSuSE 11, IP address: 10.0.0.1, Name: lx-nas.example.com
iSCSI Initiator: Windows Server 2008, Core Install, IP Address: 10.0.0.2, Name: core.example.com

Target setup:
Install openSuSE 11, any installation type + iscsitarget, iscsitarget-kmp-default
Make available one additional disk, in this case sdb
Add target by editing /etc/ietd.conf:
Target iqn.2008-09.com.example:b37d1bcc-4143-4488-8946-1adeab9dc19e
Lun 0 Path=/dev/sdb, Type=fileio

Enable & satart service
#chkconfig --set iscsitarget on
#rciscsitarget start

Initiator Setup:
Install Windows Server 2008 core

Enable & satart service
sc \\core config msiSCSI start= auto
net start msiSCSI

Setup iSCSI Intiator

iscsicli AddTargetPortal 10.0.0.1 3260
iscsicli ListTargets
Targets Lists:
iqn.2008-09.com.example:b37d1bcc-4143-4488-8946-1adeab9dc19e
iscsicli QloginTarget iqn.2008-09.com.example:b37d1bcc-4143-4488-8946-1adeab9dc19e
iscsicli PersistentLoginTarget iqn.2008-09.com.example:b37d1bcc-4143-4488-8946-1adeab9dc19e T * * * * * * * * * * * * * * * 0
iscsicli ListPersistentTargets
iscsicli ReportTargetMappings

Create partition & format

diskpart
DISKPART> rescan
DISKPART> list disk
DISKPART> select disk=1
DISKPART> online
DISKPART> create partition primary
DISKPART> format quick