Microsoft watch this. :)
No need of an OS...
http://www.vmware.com/vmworldnews/esx.html
23-03-2008
08-03-2008
Launch Windows Server 2008
Visit our booth at Heroes Happen Here on 11-12-13 March in Gent and enjoy our Demo.
INS/BT will demonstrate NAP.
See you in Gent...
JJ
INS/BT will demonstrate NAP.
See you in Gent...
JJ
05-03-2008
AD Restore
A good kb article about AD restores. I've received this link from Ward (PFE Microsoft Belgium) http://support.microsoft.com/kb/840001
MS ISCSI Initiator and Dynamic Disks
What the hell!!! Why is an iscsi lun not persistent...? It took me half a day to find out why some iscsi luns disappear after a reboot.
Dynamic disks on an iSCSI session are not supported. For best results it is recommended that basic disks be used with iSCSI. Basic Disks can be expanded in the same way that Dynamic Disks can be expanded. Please see KB325590 at http://support.microsoft.com/default.aspx?scid=kb;[LN];325590 for more information on extending a data volume on a basic disk. If you do attempt to setup a dynamic disk on an iSCSI volume,after logging into the target you may have to manually go into the disk manager and reactivate the disk. To do this, right click on the disk and select the Reactivate Disk menu item. Please see the iSCSI users guide for more information.
Dynamic disks on an iSCSI session are not supported. For best results it is recommended that basic disks be used with iSCSI. Basic Disks can be expanded in the same way that Dynamic Disks can be expanded. Please see KB325590 at http://support.microsoft.com/default.aspx?scid=kb;[LN];325590 for more information on extending a data volume on a basic disk. If you do attempt to setup a dynamic disk on an iSCSI volume,after logging into the target you may have to manually go into the disk manager and reactivate the disk. To do this, right click on the disk and select the Reactivate Disk menu item. Please see the iSCSI users guide for more information.
04-03-2008
Reseting OWA (Exchange 2003) folders in IIS
This article will help you if someone was playing around in the IIS console on an Exchange 2003 server...
http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html?printversion
http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html?printversion
Owa 2007 on Server 2008 Blank Page
These procedure needs to be followed to solve the blank page issue with OWA 2007 on Windows Server 2008.
• Remove IIS
• Reinstall IIS
• Remove CAS
• Reinstall CAS
• Remove IIS
• Reinstall IIS
• Remove CAS
• Reinstall CAS
Exchange 2007 SCR
SCR is configured so that transaction log files are being replicated for a single storage group, SG1DEMO, which contains a single database, MBX1DEMO. The paths for the storage group files and database file are C:\SG1DEMO and C:\SG1DEMO\MBX1DEMO.EDB. SITE-A-EXCHANGE is the SCR source computer and SITE-B-EXCHANGE is the SCR target computer. These assignments were configured using the following command:
Before you can create a new storage group that is enabled for SCR, you must first make sure that the paths for the storage group files, log files, and database file can be identically matched on the SCR source and all SCR target computers.
Create new Storage group
New Mailbox database
For example, if on the SCR source, the storage group files and log files are located at D:\SG1\Logs and the database is located at E:\SG1\Database, you must also have D:\SG1\Logs and E:\SG1\Database available for the path on all SCR target computers.
Note: The built-in delay of 50 log files and the value of the ReplayLagTime parameter has implications for the creation of the initial SCR target database. An SCR target database will not be created until 50 transaction log files have been replicated to the SCR target computer, and until the time period specified by ReplayLagTime (or the default ReplayLagTime value of 24 hours) has elapsed. To change the replay or truncation delay settings, you must first disable SCR, and then re-enable SCR using the new values for these settings.
Enable-StorageGroupCopy SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE -ReplayLagTime 0.0:0:0
The health and status of SCR for SG1DEMO was verified using the Test-ReplicationHealth and Get-StorageGroupCopyStatus cmdlets in the Exchange Management Shell
Get-StorageGroupCopyStatus SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE
Create log files by moving mailboxes or send mail
Create storage group and mailbox database on site B and mount it. After, dismount the database to clear the log file folder of this database.
New-StorageGroup -Server SITE-B-EXCHANGE -name SG1DEMOPORT -LogFolderPath C:\SG1DEMOPORT -SystemFolderPath C:\SG1DEMOPORT
New-MailboxDatabase -StorageGroup SITE-B-EXCHANGE\SG1DEMOPORT -Name MBX1DEMOPORT -EdbFilePath C:\SG1DEMOPORT\MBX1DEMOPORT.edb
Mount-Database MBX1DEMOPORT
Dismount-Database MBX1DEMOPORT -Confirm:$False
Del C:\SG1DEMOPORT\*.*
An application event log entry indicates that the SCR source database is physically corrupt. Because SCR was enabled for SG1DEMO, the decision is made to perform a manual activation of the SCR target database for SG1DEMO and to use database portability to restore data availability. Activation of the SCR target copy begins with dismounting MBX1DEMO in SG1DEMO using the following cmdlet
Optional, in our demo we just shut down the server.
Dismount-Database SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO -Confirm:$False
The SCR target database is then made viable for mounting, and the mailboxes originally on MBX1DEMO will be rehomed to MBX1DEMOPORT.The process for disabling SCR and making the SCR target database viable for mounting involves running the Restore-StorageGroupCopy cmdlet. This task marks the storage group's database as mountable and provides a report on the data loss, if any, that will result from mounting the database in the storage group. It also verifies that all of the log files generated by the active copy of the storage group are present in the passive copy's storage group file location. If any log files are missing, the operation will also try to copy them. The following cmdlet is used to make the SCR target database aviable for mounting:
Restore-StorageGroupCopy SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE -Force
After the Restore-StorageGroupCopy command has completed, the administrator must verify that the database is in a clean shutdown state. If the database is in a dirty shutdown state, it must be brought to a clean shutdown. If the log file prefix for the storage group (for example, E00 or E01) is the same for the SCR source (SITE-A-EXCHANGE\SG1) and the storage group on the SCR target (SG1PORT) that will be used for database portability (SITE-B-EXCHANGE\SG1PORT), running Eseutil in recovery mode is not necessary, and the final database mount operation will bring the database into a clean shutdown state after all of the replicated log files have been replayed. If the database is not in a clean shutdown state, Exchange Server Database Utilities (Eseutil) recovery mode (Eseutil /r) must be run against the database.
Eseutil /mh C:\SG1DEMO\MBX1DEMO.edb
Eseutil /r E01
Eseutil /mh C:\SG1DEMO\MBX1DEMO.edb
Once the database is in a clean shutdown state, you can run two commands that update Active Directory with new locations for the storage group files and database file. These commands change the paths for SG1DEMOPORT and MBX1DEMO from their original paths to the paths for the staged storage group and database (SG1DEMOPORT and MBX1DEMOPORT):
Move-StorageGroupPath SITE-B-EXCHANGE\SG1DEMOPORT -SystemFolderPath C:\SG1DEMO -LogFolderPath C:\SG1DEMO -ConfigurationOnly -Confirm:$False
Move-DatabasePath SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -EdbFilePath C:\SG1DEMO\MBX1DEMO.edb -ConfigurationOnly -Confirm:$False -force
The –ConfigurationOnly parameter must be included in the above commands so that only the configuration settings for these objects are updated in Active Directory. No data or files are moved, nor do they need to be because SCR has already replicated the data to C:\SG1DEMO on SITE-B-EXCHANGE.
The next step is to configure the database (MBX1DEMOPORT) to allow it to be overwritten during a restore operation. This can be done by selecting the checkbox for the setting "This database can be overwritten by a restore" on the database object properties in the Exchange Management Console or by using the following command in the Exchange Management Shell:
Set-MailboxDatabase SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -AllowFileRestore:$true
Mount-Database MBX1DEMOPORT\
At this point, client access to MBX1DEMOPORT is now possible. However, whether users can actually access their mailboxes after they have been moved from SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO to SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT depends on Active Directory replication latency; that is, depending on the number of directory servers, it may take time for the update to propagate throughout the environment. In addition, client access methods matter. Messaging clients running Outlook 2007 and non-Outlook clients will have access to the user's mailbox after the directory servers used by the user's Client Access server have been updated with the new paths. Messaging clients running Outlook 2003 and earlier versions will require the user's desktop messaging profile to be updated with the new server name.
Get-Mailbox -Database SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO where {$_.ObjectClass -NotMatch '(SystemAttendantMailboxExOleDbSystemMailbox)'} Move-Mailbox -ConfigurationOnly -TargetDatabase SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -Confirm:$False
After clients have access to their mailboxes and mailbox data, the final step is to establish redundancy by re-enabling SCR. This is done by removing any remaining storage group and database files from SITE-A-EXCHANGE. After the files have been removed, the paths for SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO can be moved to a temporary location and SITE-A-EXCHANGE can become an SCR target of SITE-B-EXCHANGE.
Via script: save this code in a file like as .ps1. You need to modify the script and provide your Exx number for ESUTIL.
Restore-StorageGroupCopy SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE –force
cd c:\SG1DEMO
Eseutil /r E04 /i /a
Move-StorageGroupPath SITE-B-EXCHANGE\SG1DEMOPORT -SystemFolderPath C:\SG1DEMO -LogFolderPath C:\SG1DEMO -ConfigurationOnly -Confirm:$False
Move-DatabasePath SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -EdbFilePath C:\SG1DEMO\MBX1DEMO.edb -ConfigurationOnly -force
Set-MailboxDatabase SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -AllowFileRestore:$true
Mount-Database MBX1DEMOPORT
Get-mailbox -database site-a-exchange\sg1demo\mbx1demo where {$_.objectclass -notmatch '(systemattendantmailboxexoledbsystemmailbox)'} move-mailbox -configurationonly -targetdatabase site-b-exchange\sg1demoport\mbx1demoport -confirm:$false
Before you can create a new storage group that is enabled for SCR, you must first make sure that the paths for the storage group files, log files, and database file can be identically matched on the SCR source and all SCR target computers.
Create new Storage group
New Mailbox database
For example, if on the SCR source, the storage group files and log files are located at D:\SG1\Logs and the database is located at E:\SG1\Database, you must also have D:\SG1\Logs and E:\SG1\Database available for the path on all SCR target computers.
Note: The built-in delay of 50 log files and the value of the ReplayLagTime parameter has implications for the creation of the initial SCR target database. An SCR target database will not be created until 50 transaction log files have been replicated to the SCR target computer, and until the time period specified by ReplayLagTime (or the default ReplayLagTime value of 24 hours) has elapsed. To change the replay or truncation delay settings, you must first disable SCR, and then re-enable SCR using the new values for these settings.
Enable-StorageGroupCopy SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE -ReplayLagTime 0.0:0:0
The health and status of SCR for SG1DEMO was verified using the Test-ReplicationHealth and Get-StorageGroupCopyStatus cmdlets in the Exchange Management Shell
Get-StorageGroupCopyStatus SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE
Create log files by moving mailboxes or send mail
Create storage group and mailbox database on site B and mount it. After, dismount the database to clear the log file folder of this database.
New-StorageGroup -Server SITE-B-EXCHANGE -name SG1DEMOPORT -LogFolderPath C:\SG1DEMOPORT -SystemFolderPath C:\SG1DEMOPORT
New-MailboxDatabase -StorageGroup SITE-B-EXCHANGE\SG1DEMOPORT -Name MBX1DEMOPORT -EdbFilePath C:\SG1DEMOPORT\MBX1DEMOPORT.edb
Mount-Database MBX1DEMOPORT
Dismount-Database MBX1DEMOPORT -Confirm:$False
Del C:\SG1DEMOPORT\*.*
An application event log entry indicates that the SCR source database is physically corrupt. Because SCR was enabled for SG1DEMO, the decision is made to perform a manual activation of the SCR target database for SG1DEMO and to use database portability to restore data availability. Activation of the SCR target copy begins with dismounting MBX1DEMO in SG1DEMO using the following cmdlet
Optional, in our demo we just shut down the server.
Dismount-Database SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO -Confirm:$False
The SCR target database is then made viable for mounting, and the mailboxes originally on MBX1DEMO will be rehomed to MBX1DEMOPORT.The process for disabling SCR and making the SCR target database viable for mounting involves running the Restore-StorageGroupCopy cmdlet. This task marks the storage group's database as mountable and provides a report on the data loss, if any, that will result from mounting the database in the storage group. It also verifies that all of the log files generated by the active copy of the storage group are present in the passive copy's storage group file location. If any log files are missing, the operation will also try to copy them. The following cmdlet is used to make the SCR target database aviable for mounting:
Restore-StorageGroupCopy SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE -Force
After the Restore-StorageGroupCopy command has completed, the administrator must verify that the database is in a clean shutdown state. If the database is in a dirty shutdown state, it must be brought to a clean shutdown. If the log file prefix for the storage group (for example, E00 or E01) is the same for the SCR source (SITE-A-EXCHANGE\SG1) and the storage group on the SCR target (SG1PORT) that will be used for database portability (SITE-B-EXCHANGE\SG1PORT), running Eseutil in recovery mode is not necessary, and the final database mount operation will bring the database into a clean shutdown state after all of the replicated log files have been replayed. If the database is not in a clean shutdown state, Exchange Server Database Utilities (Eseutil) recovery mode (Eseutil /r) must be run against the database.
Eseutil /mh C:\SG1DEMO\MBX1DEMO.edb
Eseutil /r E01
Eseutil /mh C:\SG1DEMO\MBX1DEMO.edb
Once the database is in a clean shutdown state, you can run two commands that update Active Directory with new locations for the storage group files and database file. These commands change the paths for SG1DEMOPORT and MBX1DEMO from their original paths to the paths for the staged storage group and database (SG1DEMOPORT and MBX1DEMOPORT):
Move-StorageGroupPath SITE-B-EXCHANGE\SG1DEMOPORT -SystemFolderPath C:\SG1DEMO -LogFolderPath C:\SG1DEMO -ConfigurationOnly -Confirm:$False
Move-DatabasePath SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -EdbFilePath C:\SG1DEMO\MBX1DEMO.edb -ConfigurationOnly -Confirm:$False -force
The –ConfigurationOnly parameter must be included in the above commands so that only the configuration settings for these objects are updated in Active Directory. No data or files are moved, nor do they need to be because SCR has already replicated the data to C:\SG1DEMO on SITE-B-EXCHANGE.
The next step is to configure the database (MBX1DEMOPORT) to allow it to be overwritten during a restore operation. This can be done by selecting the checkbox for the setting "This database can be overwritten by a restore" on the database object properties in the Exchange Management Console or by using the following command in the Exchange Management Shell:
Set-MailboxDatabase SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -AllowFileRestore:$true
Mount-Database MBX1DEMOPORT\
At this point, client access to MBX1DEMOPORT is now possible. However, whether users can actually access their mailboxes after they have been moved from SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO to SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT depends on Active Directory replication latency; that is, depending on the number of directory servers, it may take time for the update to propagate throughout the environment. In addition, client access methods matter. Messaging clients running Outlook 2007 and non-Outlook clients will have access to the user's mailbox after the directory servers used by the user's Client Access server have been updated with the new paths. Messaging clients running Outlook 2003 and earlier versions will require the user's desktop messaging profile to be updated with the new server name.
Get-Mailbox -Database SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO where {$_.ObjectClass -NotMatch '(SystemAttendantMailboxExOleDbSystemMailbox)'} Move-Mailbox -ConfigurationOnly -TargetDatabase SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -Confirm:$False
After clients have access to their mailboxes and mailbox data, the final step is to establish redundancy by re-enabling SCR. This is done by removing any remaining storage group and database files from SITE-A-EXCHANGE. After the files have been removed, the paths for SITE-A-EXCHANGE\SG1DEMO\MBX1DEMO can be moved to a temporary location and SITE-A-EXCHANGE can become an SCR target of SITE-B-EXCHANGE.
Via script: save this code in a file like as .ps1. You need to modify the script and provide your Exx number for ESUTIL.
Restore-StorageGroupCopy SITE-A-EXCHANGE\SG1DEMO -StandbyMachine SITE-B-EXCHANGE –force
cd c:\SG1DEMO
Eseutil /r E04 /i /a
Move-StorageGroupPath SITE-B-EXCHANGE\SG1DEMOPORT -SystemFolderPath C:\SG1DEMO -LogFolderPath C:\SG1DEMO -ConfigurationOnly -Confirm:$False
Move-DatabasePath SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -EdbFilePath C:\SG1DEMO\MBX1DEMO.edb -ConfigurationOnly -force
Set-MailboxDatabase SITE-B-EXCHANGE\SG1DEMOPORT\MBX1DEMOPORT -AllowFileRestore:$true
Mount-Database MBX1DEMOPORT
Get-mailbox -database site-a-exchange\sg1demo\mbx1demo where {$_.objectclass -notmatch '(systemattendantmailboxexoledbsystemmailbox)'} move-mailbox -configurationonly -targetdatabase site-b-exchange\sg1demoport\mbx1demoport -confirm:$false
Abonneren op:
Posts (Atom)
