Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBs. All these updates may become available on the Download Center, and also through Windows Update.

These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

The TechNet article Exchange 2010 Prerequisites is updated with the hotfixes and install the prerequisites required for your server version (the hotfixes are linked to in the above table).

You can use the Install the Windows Server 2008 SP2 operating system prerequisites on a Windows 2008 R2 server. Only you have to run the following powershell command: Import-Module ServerManager

Installed Exchange 2010 SP1 on a Windows 2008 R2 Server with problems. I feels that the MMC is faster. Tomorrow upgrading a DAG/NLB cluster to Exchange 2010 SP1.

Here is a list of the just some of technologies that this book talks about to achieve a Least Privilege Security:

• Program Compatibility Wizard
• Applications Compatibility Wizard
• User Account Control
• Group Policy Software Deployment
• Internet Explorer Add-on Management
• Troubleshooting Remote Users
• Configuring Windows Firewall
• Software Restrictions Policies and AppLocker
• Microsoft Deployment Toolkit
• CD Burning
• ActiveX Controls
• Changing system time and time zones
• Power Management
• Managing networks
• Standard Users Analyzer
• Applications Compatibility Toolkit
• Logon Scripts
• Remote Desktop Services
• App-V
• Med-V

I have read already some chapters. I think it is a great book to have on your collection.
You have always not enough time thinking about security. This book does it for you.

As a special offer Packt Publishing are also letting people download preview chapter of this book by download here Chapter No. 3 – Solving Least privilege Problems with the Application Compatibility Toolkit

What’s New in VMware Workstation 7.1

Download the beta now at https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=8689

MDT 2010 Update 1 provides new capabilities, such as:

· Support for Microsoft Office 2010.

· A new User-driven Installation (UDI) deployment method (formerly known as “Modena”) for Microsoft System Center Configuration Manager 2007. UDI gives information technology (IT) staff control over the deployment experience while empowering users to interact with and customize their operating system deployment through an easy-to-use wizard.

· Improvements to the Deployment Workbench driver import process, detecting each driver’s true supported platforms.

· Many bug fixes and other small improvements.

This release supports the deployment of the Windows® 7; Windows Vista®; Windows XP; Windows Server® 2008 R2; Windows Server 2008; and Windows Server 2003 operating systems. See the Microsoft Deployment Toolkit Documentation Library, which is included with MDT 2010 Update 1, for the complete documentation for this release.

• Verify an application’s compatibility with a new version of the Windows operating system, or a Windows Update, including determining your risk assessment.
• Become involved in the ACT Community, including sharing your risk assessment with other ACT users.
• Test your Web applications and Web sites for compatibility with new releases and security updates to the Windows® Internet Explorer® Internet browser.

Software Requirements:

Download HERE

You can use MAP to inventory the following platforms:

• Windows 7
• Windows Vista
• Windows XP® Professional
• Windows Server 2008 or Windows Server 2008 R2
• Windows Server 2003 or Windows Server 2003 R2
• Windows 2000 Professional or Windows 2000 Server
• VMware ESX
• VMware ESXi
• VMware Server

Reporting
- Identification of currently installed Windows client operating systems, their hardware, and recommendations for migration to Windows 7 and Windows Vista. The tool also reports if desktops have anti-virus and anti-malware programs installed and if the Windows Firewall is turned on.
- Identification of currently installed Windows Server operating systems, their hardware, and recommendations for migration to Windows Server 2008 R2 and Windows Server 2008.
- Identification of currently installed Microsoft Office software and recommendations for migration to Microsoft Office 2007.
- Detailed assessment and reporting of server utilization gathered using the Performance Metrics Wizard.
- Recommendations for server consolidation and virtual machine placement using Hyper-V
- Assessment of client machines, servers, and the technology environment for the implementation of Microsoft Application Virtualization (APP-V)
- Identification of machines where Microsoft SQL Server components are installed.
- Identification of virtual machines, their hosts, and details about each.
- Identification of Windows Server Roles

Hardware Requirements:
- Windows 2003 x86/x64 or Windows 2008 x86/x64
- 1,5 GB (2 GB 2008)

Software Requirements:
- NET Framework 3.5 SP1
- Windows Installer 4.5
- Microsoft Office Word 2007 or Word 2003 SP2
- MIcrosoft Office Excel 2007 or Excel 2003 SP2
- SQL Server 2008 Express Edition, SQL Server 2008, or SQL Server 2005

Download Microsoft Assessment and Planning (MAP) Toolkit HIER

Handleidingen:
Healthcare Desktop User State Migration Guide
Automated Build Application Integration Guide
Healthcare MDT 2010 Administrators Guide
Automated Build Healthcare Desktop and Server Guide

Downloaden van de MDT HealthCare doe je hier: MDT HealthCare

Installatie:

Voorbeeld wat Health Care automatisch aanmaakt:

Een ex-collega Duncan Epping had ook een blog. Genaamd Yellow Bricks.
Ik vond wel interessant dat bloggen. Dus ook maar gaan bloggen over VMWare & Microsoft.

Een dikke jaar later zijn de statistieken als volgt zonder bots:
74.588 Unieke bezoekers
167.496 Hits

Het aantal hits schommelt tussen de 700 en 1500 hits per dag.

Voor de desbetreffende Windows 7 & Windows Vista & Windows 2008 & Windows 2008 R2 task
klik properties en ga dan naar het tabblad OS info. Klik op Unattend.xml
 
Onder oobeSystem –> amd64_Microsoft-Windows-Shell-Setup_neutral –> UserAccounts –> AdministratorPassword

De volgende nieuwe OS worden ondersteund:
- Windows 7 Home Basic
- Windows 7 Premium
- Windows 7 Business
- Windows 7 Enterprise
- Windows 7 Ultimate
- Windows 2008 SP2, R2
- Windows Vista SP2

Nieuwe Features:
- Windows 7
- Aero
- Windows XP Mode Compatible
- 3D Graphics Verbeteringen voor Windows XP gasten
- vSphere Support ESX 4.0 Overwegingen voor het draaien van een ESX gast.
- Virtuele Printing
- Four-way SMP
- Guest 32GB Memory
- 256-bit Encryption
- AutoProtect
- Advanced Linux Sound Architecture (ALSA
- Cross-Platform License Keys
- Pauzeer een Virtual Machine
- Expand virtuele schijven
- Compact virtuele schijven
- Shared Folder Compatibiliteit
- On-Demand VMware Tools Download
- Drag and Drop Enhancements
- Virtual Network Editor
- Fuse Mount voor Linux
- Vereenvoudigde Verzamelen van Informatie over ondersteuning
- IPv6 Support

Officiële Release Notos vind je HIER

 Michael Niehaus heeft een overzicht gemaakt van alle nieuwe functies en stuk voor stuk uitlegt wat het doet. Ik heb even een mooi overzicht van gemaakt:

Automatically update MDT 2010 boot images in WDS
Automating Long-Running MDT 2010 Tasks

MDT 2010 New Feature #1: Logging directly to the network
MDT 2010 New Feature #2: Gathering virtualization details
MDT 2010 New Feature #3: Suspend and resume a Lite Touch task sequence
MDT 2010 New Feature #4: Folders everywhere
MDT 2010 New Feature #5: Support for multiple deployment shares
MDT 2010 New Feature #6: Drag and drop
MDT 2010 New Feature #7: Boot image creation optimized
MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE
MDT 2010 New Feature #9: Copy and paste support in the Deployment Workbench task sequence editor
MDT 2010 New Feature #10: Detection of signed drivers
MDT 2010 New Feature #11: Windows 7 and Windows Server 2008 R2 support
MDT 2010 New Feature #12: USMT 4.0 hardlink support
MDT 2010 New Feature #13: New task sequence templates
MDT 2010 New Feature #14: Database improvements
MDT 2010 New Feature #15: Finish actions
MDT 2010 New Feature #16: PowerShell support
MDT 2010 New Feature #17: Customizable boot image process
MDT 2010 New Feature #18: Selection Profiles
MDT 2010 New Feature #19: Improved Driver Management
MDT 2010 New Feature #20: General Purpose ConfigMgr wizard
MDT 2010 New Feature #21: Copying extra folders

De onthulling dat Windows 7 in het vierde kwartaal verschijnt, werd gedaan op de maandag begonnen Microsoft Tech Ed-conferentie te Los Angeles, aldus Microsofts Windows Blog. Een definitieve releasedatum werd nog niet bekent gemaakt. Hoewel al enige tijd wordt verwacht dat het nieuwe besturingssysteem in het najaar verschijnt. Het standpunt van Microsoft was tot dus ver dat het OS maximaal drie jaar na de release van Vista op de markt zou komen, oftewel niet later dan 30 januari 2010. Microsoft heeft overigens voorts laten weten dat ook Windows Server 2008 R2 in het vierde kwartaal wordt vrijgegeven.

 

De beta van Exchange 2010 wordt alleen op Windows 2008 x64 standaard of Enterprise door Microsoft ondersteund. Windows 2008 R2 kan het wel in werken maar het wordt nog niet ondersteund. Zie voor Exchange 2010 blog voor meer infomatie.

Look here for Prepare Active Directory and Domains.

Algemene Voorbereiding

1. Install Microsoft .NET Framework 3.5.
2. Install Windows Remote Management ( WinRM ) 2.0 Community Technology Preview 3 (CTP3).
3. Install Windows PowerShell V2 CTP3.

4. Install the update for the Microsoft Management Console (MMC) in Windows Server 2008. See Microsoft Knowledge Base article 951725 An update that extends the mechanism for displaying snap-in context Help topics is available for the MMC in Windows Server 2008.

5. Update from KB 951725
Update from KB 950888
Update from KB 951116
Update from KB 952664
Update from KB 953290
Update from KB 958178

Client Access servers

1. Install the Active Directory remote management tools by running the following command:

ServerManagerCmd -i RSAT-ADDS

2. Install the extensions for ASP.NET AJAX 1.0.

3. Install the necessary Internet Information Services (IIS) prerequisites by running the following commands in the order in which they are listed:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Digest-Auth

ServerManagerCmd -i Web-Windows-Auth

ServerManagerCmd -i Web-Dyn-Compression

ServerManagerCmd -i NET-HTTP-Activation

ServerManagerCmd -I RPC-over-HTTP-proxy

Edge Transport servers

1. Install Active Directory Lightweight Directory Services (AD LDS), which was previously known as Active Directory Application Mode (ADAM), by running the following command:

ServerManagerCmd -i ADLDS

Hub Transport servers

1. Install the Active Directory remote management tools by running the following command:

ServerManagerCmd -i RSAT-ADDS

1. Install the extensions for ASP.NET AJAX 1.0.
2. Install the necessary Internet Information Services (IIS) prerequisites:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

Mailbox servers

1. Install the Active Directory management tools by running the following command:

ServerManagerCmd -i RSAT-ADDS

1. Install the extensions for ASP.NET AJAX 1.0.
2. Install the 2007 Office System Converter: Microsoft Filter Pack.
3. Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

Clustered Mailbox
5. ServerManagerCmd -i Failover-Clustering

Unified Messaging servers

1. Install the extensions for ASP.NET AJAX 1.0.
2. Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

1. Install the Microsoft Windows Media Player audio/video codecs required by the Unified Messaging server by running the following command:

Copy Code

ServerManagerCmd -i Desktop-Experience

Exchange Management Tools

1. Install the necessary IIS prerequisites by running the following commands:

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

To install the latest optional Windows Updates

1. Install multiple Right Management Services (RMS) Client sessions update. See Knowledge Base article 950888 You cannot create multiple RMS Client sessions for one user context on a Windows Vista-based computer.
2. Install performance counter updates. See Knowledge Base article 951116 A memory leak occurs in performance counters that are used to monitor Windows Server 2008-based computers.
3. Install the System Center Operations Manager 2007 console update. See Knowledge Base article 951327 The System Center Operations Manager 2007 console may crash in Windows Server 2008 or in Windows Vista when you open the Health Explorer window.
4. Install the Event Log service update. See Knowledge Base article 952664 The Event Log service may stop responding because of a deadlock on a Windows Server 2008-based computer.
5. Install performance counter values update. See Knowledge Base article 953290 An application may crash when it uses legacy methods to query performance counter values in Windows Vista or in Windows Server 2008.
6. Install Windows PowerShell V2 CTP3.

What’s New
Server 2.0.1 is a maintenance release that resolves security as well as some known issues. With this release of VMware Server, certain new features and support have been added.
Support for New Guest Operating Systems
VMware provides support for the following operating systems for Server 2.0.1:

• Asianux Server 3.0 Service Pack 1
• CentoOS 4.7
• CentOS 5.2
• Windows Essential Business Server (EBS) and Small Business Server (SBS) 2008
• Windows Small Business Server 2003 Service Pack 2
• Windows XP Service Pack 3
• Windows Vista Service Pack 1

Security Fixes:

• VMnc codec heap overflow vulnerabilities
  The VMnc codec assists in record and replay of sessions which are records of the dynamic virtual machine state over a period of time. Two heap overflow vulnerabilities might allow a remote attacker to execute arbitrary code on VMware hosted products. For an attack to be successful, the user must visit a malicious Web page or open a malicious video file. The Common Vulnerabilities and Exposures project has assigned the names CVE-2009-0909 and CVE-2009-0910 to these issues.
• A VMCI privilege escalation on Windows-based hosts or Windows-based guests
  The Virtual Machine Communication Interface (VMCI) provides fast and efficient communication between two or more virtual machines on the same host and between a virtual machine and the host operating system. A vulnerability in vmci.sys might allow privilege escalation on Windows-based machines. This might occur on Windows-based hosts or inside Windows-based guest operating systems. Current versions of ESX Server do not support the VMCI interface and hence they are not affected by this vulnerability. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1147 to this issue.
• A remote denial-of-service vulnerability in authd for Windows-based hosts
  A vulnerability in vmware-authd.exe might cause a denial-of-service condition on Windows hosts. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-0177 to this issue.
• Updated vm-support script
  This release improves data collection when the vm-support script is run by the Server administrator on request of VMware support or its support partners. The file that contains the SSL keys for communication between Server and vCenter and other applications is no longer collected. For more details, see the KB article Data Security Best Practices – SSL keys for communicating with VirtualCenter and other applications (KB 1008166).
• Windows-based host privilege escalation in hcmon.sys
  A vulnerability in an I/O Control (ioctl) function in hcmon.sys might be used to escalate privileges on a Windows-based host. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1146 to this issue. New releases of hosted products address a denial-of-service problem described in CVE-2008-3761, which can only be exploited by a privileged Windows account.
• Denial-of -service vulnerability in a virtual device
  A vulnerability in a guest virtual device driver might allow a guest operating system to cause the host and consequently any virtual machine on that host to fail. The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-4916 to this issue.

Miscellaneous Fixes:

• Mount installer option mounts current CD-ROM image instead of VMware Tools installer image
  If a CD-ROM image is mounted to a virtual machine with VMware Tools installed, the Mount installer option in the Web UI incorrectly mounts the CD-ROM image instead of the VMware Tools image. The issue is resolved in this release.
• Unable to install the latest version of VIX API on Server 2.0.x
  You cannot install VMware VIX API 1.6.2 of due to an issue with the MSI installer for VIX API. This issue is resolved in this release.
• The default VI Web Access HTTP connection port is 8222 and the default HTTPS port is 8333. If you use these defaults, or any values other than 80 (HTTP) and 443 (HTTPS), you must specify the port number when you connect to VMware Server using VI Web Access. You must also allow connection to these ports through your firewall. An example URL to connect to VI Web Access is http://server_host:8222 If you want to use ports 80 (HTTP) and 443 (HTTPS), override the default values during installation. Note: If you are running IIS or Apache web server on the default ports, specify alternate HTTP and HTTP ports when prompted by the Windows installer or vmware-config.pl. Alternatively, stop IIS’s default Web site or any other Web site running on these ports. On Linux, shut down Apache or any other application using these ports and make sure they are not configured to restart automatically. This issue is resolved in this release.

2. Maak de volgende structuur lijkend op deze
D:Distribution
-Operating System
–Windows Server 2003 R2 Enterprise SP2 Eng x86
—$OEM$
—-$1
—–R2

3. Van de Windows Server 2003 R2 CD2, kopieer de CMPNENTS map naar D:DistributionOperating SystemsWindows Server 2003 R2 Enterprise SP2 Eng x86$OEM$$1R2

4. In de OEM$$1R2 map maak een batch bestand aan genaamd InstallR2.cmd (met de onderstaande tekst er in)

reg add HKLMSoftwareMicrosoftWindowsCurrentVersionSetup /v SourcePath /t REG_SZ /d C:WindowsSourcei386 /f
reg add HKLMSoftwareMicrosoftWindowsCurrentVersionSetup /v ServicePackSourcePath /t REG_SZ /d C:R2CMPNENTSR2 /f
C:\R2CMPNENTSR2setup2.exe /q /a /sr

Opmerking: Er zijn 3 regels. Regel 1 & 2 beginnen met  "reg", regel 3 begint met "C:R2".

4. Pas de Windows Server 2003 R2 X86 Task Sequence aan.
Pas de [GUIRunOnce] sectie in Unattend.txt aan zoals het hier onderstaat:
[GUIRunOnce]
    "C:R2InstallR2.cmd"
    "cscript.exe C:MININTScriptsLiteTouch.wsf /start"
    "cscript.exe D:MININTScriptsLiteTouch.wsf /start"
    "cscript.exe E:MININTScriptsLiteTouch.wsf /start"
    "cscript.exe F:MININTScriptsLiteTouch.wsf /start"

Opmerking: Wil je de melding Windows Server Post-Setup Security Updates scherm niet krijgen moet je onder staan regel gebruiken.

Option 1:

Set "HKLMSoftwareMicrosoftWindowsCurrentVersionServerOOBESecurityOOBEDontLaunchSecurityOOBE" to "0"

Option 2:

Wil je Windows Firewall uitgeschakeld hebben voeg deze regels dan toe in unattend.xml

[WindowsFirewall]
Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]
Mode = 0

BRON

Wil je MDT inrichten op Windows 2008 server. Dan zul moet je gebruik maken van de volgende waik versie.

http://www.microsoft.com/downloads/details.aspx?familyid=94BB6E34-D890-4932-81A5-5B50C657DE08&displaylang=en

http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true

Je moet x64 aanzetten als je 64bits OS wilt uitrollen via WDS zie het volgende stukje tekst:

• x64-based client computers do not receive an x64 Windows PE boot image. This can occur if the PXE basic input/output system (BIOS) implementation of the network booting computer does not correctly identify itself as being capable of working with x64-based computers. To work around this issue, enable architecture detection in the boot programs. To do this, run this command on your WDS server:

Commando: WDSUTIL /set-server /architecturediscovery:yes

Windows Server 2008 ondersteund support Serial Attached SCSI (SAS), iSCSI en Fibre Channel disks als opslag opties. Aan het einde van deze heb een twee node cluster draaien met gedeelde iSCSI opslag.

Wat je nodig hebt.

· Windows Vista / XP / 2003 / 2008 pc server met 4GB geheugen dus de x64 versie.

· Een Windows Server 2003 of Windows 2008 VM die fungeert als een domein controller

· De domain controller inrichten met 3 VM harddisk 1 voor OS 2 voor Storage

· Twee Windows 2008 Enterprise VM’s die als cluster gaan fungeren.

· Zorg dat de 2 Windows 2008 Enterprise VM’s voorzien zijn van 3 NICS

· Zorg dat op de twee Windows 2008 Enterprise VM’s de cluster management software is geïnstalleerd.

· iSCSI software. Ik heb hiervoor RocketDevision StarWind waarvan een 30 dagen trail is te downloaden en je hebt een gratis versie maar die ondersteund maar 1 gelijktijdige connectie.

Opmerking:
Tijdens het maken van de cluster kun je een foutmelding krijgen: The operating system SKU is not compatible
Hier heeft microsoft een Fix voor gemaakt http://support.microsoft.com/?kbid=950179
Deze moet je downloaden en installeren.

VIRTUAL NETWORK

Ik heb 3 VLAN’s gebruikt om alles voor elkaar te krijgen.

VLAN ids:

• VLAN 2: Public 10.1.1.x/24
• VLAN 3: Heartbeat 192.168.1.x/24
• VLAN 4: iSCSI 192.168.2.x/24

SERVER SETUP

TIP: Hernoem elke netwerk kaart waar hij voor dient dus Public, Heartbeat, iSCSI

Domain Controller: dc01

• Windows Server 2003 x32 
• 1 VHD IDE fixed size disk 10GB
• 2 SCSI DISKS fixed 8GB
• StarWind iSCSI Target Software
• 1 x NIC connected to my Virtual Network in VLAN 2

Netwerk Settings:

• IP Address: 10.1.1.10
• Mask: 255.255.255.0
• Gateway: Niet nodig
• DNS: 10.1.1.10

Cluster Nodes:

• Windows Server 2008 x64
• 1 x VHD IDE fixed size disk 10GB
• 3  x NICs geconnect naar de volgende VLANs
  • Public card: VLAN 2
  • Heartbeat card: VLAN3
  • iSCSI: VLAN4

iSCSI NIC: VLAN 4

• IP Address: 192.168.2.2
• Mask: 255.255.255.0

NODE1

Public NIC: VLAN 2

• IP Address: 10.1.1.20
• Mask: 255.255.255.0
• Gateway: NIET NODIG
• DNS: 10.1.1.10

Heartbeat NIC: VLAN 3

• IP Address: 192.168.1.4
• Mask: 255.255.255.0

iSCSI NIC: VLAN 4

• IP Address: 192.168.2.4
• Mask: 255.255.255.0

Opmerking: Zorg voor alle NIC’s die in VLAN 3&4 zitten dat Client voor Microsoft Netwerks uitgezet is. Zorg ook dat DNS registratie en Netbios ook uitgezet is. Zorg ook dat de Public NIC als eerste in de Binding order staat

NODE2

Public NIC: VLAN 2

• IP Address: 10.1.1.21
• Mask: 255.255.255.0
• Gateway: NIET NODIG
• DNS: 10.1.1.10

Heartbeat NIC: VLAN 3

• IP Address: 192.168.1.5
• Mask: 255.255.255.0

iSCSI NIC: VLAN 4

• IP Address: 192.168.2.5
• Mask: 255.255.255.0

Opmerking: Zorg voor alle NIC’s die in VLAN 3&4 zitten dat Client voor Microsoft Netwerks uitgezet is. Zorg ook dat DNS registratie en Netbios ook uitgezet is. Zorg ook dat de Public NIC als eerste in de Binding order staat

Opzetten van de Cluster

Configureren van iSCSI target software (Starwind)

· Install de StarWind Software op domein controller VM (Dit is toch maar test)

· Open de StarWind Management console

· Onder de Connections zie je localhost:3260
Klik rechts op localhost and kies voor Connect. Standaard username vind je op de site van Starwind of de handleiding. Je kunt dit later wijzigen.

• Klik rechts op localhost:3260 en klik op add Device
• Kies voor Disk Bridge Device als Device Type en klik op Next

• Selecteer de eerste SCSI disk van de lijst (Lijkt op \.PhysicalDisk1). 

• Selecteer Asyncronous Mode en Allow multiple iSCSI connections (clustering) en klik op next 
• Geef de harddisk een vriendelijke naam
• Herhaal deze stappen voor de tweede disk

De DISKS toevoegen aan de Cluster

Elke cluster node moet gekoppeld worden aan de iSCSI target. Open de iSCSI initiator en volg de stappen hieronder.

• Als je de melding krijgt om de Microsoft iSCSI service vrij tegen klik op op Yes anders gaat Windows poort 3260 blokkeren.
• Klik op de Discovery tab en kies voor Add Portal.
• Geef het IP address op voor de iSCSI target [192.168.2.2]

• Klik op de Targets Tab en je zou een lijst moeten krijgen van beschikbare hardschijven van de target.

• Voor elke harde schijf klik op LOG ON en zet een vinkje bij Automatically restore this connection
• Klik op de Volumes and Devices en select Auto Configure. De harde schijven moeten gaan verschijnen als Devices
• Herstart elk cluster node als je de harde schijven hebt toegevoegd.
• De harde schijven zijn offline als je opnieuw opgestart hebt. Zorg dat de harde schijven online brengt in Disk Management.

Als je klaar bent en de harde schijven hebt dan moet je dit in Starwind zien verschijnen.

Installeren van de Cluster

De nieuwe cluster wizard is heel simpel en stelt niks voor.
Microsoft heeft zelf hiervoor een mooi handleiding geschreven.

Hier is de stap voor stap handleiding voor het installeren van twee node cluster in Windows 2008

Het probleem ontstaat waarneer update KB932596 geïnstalleerd wordt.

Via de Microsoft KB950772 zelf is hij te krijgen of via www.hotfixr.com

Run a command prompt as administrator. From the start menu, select “All Programs”, then “Accessories” and right-click on the “Command Prompt” shortcut and choose “Run As Administrator”. From here you can use the following command to disable Data Execution Prevention (DEP) with the following command:

bcdedit.exe /set {current} nx AlwaysOff (Dit was de oplossing)

Keeping your command prompt open, run your setup or other process being stopped by DEP. Then, to turn it back on again, do the same and run the following:

bcdedit.exe /set {current} nx AlwaysOn