When you set up a RES environment, you also want to give the users there profiles. Which type of profiles, that depands on your environment, but in this example I’ll use Mandatory profiles. This means the same profile for all the users and savind the custom settings per user by using User Preferences within RES PowerFuse. I very nice solutions with the best performance.
The first step is to create a fresh Mandatory Profile.
1.) Create a new local user on a Windows 2003 Server machine and make that user member of the Local Administrators Group.
2.) Login with that that user.
3.) Make your changes.
4.) Right-click on your computer, Properties, Advanced, Settings (unther User Profiles).
5.) Select your template user and click Copy To
6.) Browse to your share on your server.
7.) Change Permitted to use to Everyone Full Controll.
8.) The last step is to rename your NTUSER.dat to NTUSER.man, this makes your profile Mandatory (Read-Only).
Now we’re going to publish this mandatory profile to all the RES PowerFuse Agents, so the Mandatory profile is present on each PC with the RES PowerFuse Agent.
1.) Open your RES PowerFuse Management Console.
2.) Click on RES PowerFuse Setup, Datastore, Custom Resources
3.) Click on Add, browse to your Mandatory Profile share
As you can see, there’s now your Mandatory Profile. It will be published to all the RES PowerFuse Agents. The default location is: C:\Program Files\RES PowerFuse\Data\DBCache\Resources\custom-resources
The last step is to edit the profile path from your Active Directory Users.
1.) Open Active Directory Users and Computers on your Domain Controller.
2.) Locate your users
3.) Select one or more users and click Properties
4.) Go to the Terminal Services Profile tab
5.) Type in the path to the local Mandatory Profile
C:\Program Files\RES PowerFuse\Data\DBCache\Resources\custom_resources\Mandatory-2003
Now the users are ready to login on your Terminal Server environment with RES PowerFuse. 
Posted in RES Powerfuse | No Comments »
When you want to restore some deleted computer objects, user object or even Organizational Units back to to your production Active Directory, there’s a nice tool called ADRESTORE. It’s a tool you can download from SysInternals and it’s easy to use!
For this example I’ve deleted the OU (Organizational Unit) where my computer objects are placed. The consequenses….Yes, the computers are not longer trusted to this domain, OOPS!! 
By default the Active Directory markes all the deleted objects as IsDeleted True. The objects are not vissible any more in your Active Directory, but they still there. This calls tombstoned objects. By default tombstoned objects will be available for 60 days in a Windows 2000/2003 Active Directory and 180 days in a Windows 2003 SP1 of 2008 Active Directory.
As you can see, I’ve deleted the OU Omgeving with the sub OU’s Laptop and PC and all the computers objects in this OU’s. Now we’re going to restore everything back! Note: make sure you first restore the highest OU, than the sub OU’s and finally the computer objects.
1.) Start the command prompt (Start, Run, CMD)
2.) Locate ADRESTORE.EXE
3.) Type in ADRESTORE -R Omge* (this will find all deleted object starting with Omge)
4.) Restore the OU Omgeving by pressing Y
5.) Type in ADRESTORE -R Lap* (this will find all deleted object starting with Lap)
6.) Restore the OU Laptop by pressing Y
7.) Type in ADRESTORE -R PC
8.) Restore the OU PC by pressing Y
9.) Type in ADRESTORE -R PC* (this will find all deleted objects starting with PC)
10.) Restore the computer objects PC01 till PC10 by pressing Y
11.) 9.) Type in ADRESTORE -R LT* (this will find all deleted objects starting with LT)
10.) Restore the computer objects LT01 till LT10 by pressing Y
When you’ve restored all the objects, these are disabled by default, so you’ve to enabled them manually!
Posted in Microsoft Exchange 2003 Server | 42 Comments »
If you are like me, you were both excited and surprised to see Windows Storage Server 2008 available for download from the MSDN Subscriber Site. Unlike other Windows 2008 Server installations, Storage Server never asks you to create an Administrator password, so you are stuck at a login prompt with no idea on how to login.
Well, I’ve done the scouring for you and the default password is wSS2008!
Hopefully that helps someone out!
Posted in Microsoft Windows 2008 Server | No Comments »
A cool new feature in Windows Server 2008 are the User Preferences. With this user preferences you’re able to create a lot of things, such as:
- Drive Maps
- Environment variables
- Files
- Folders
- Ini files
- Registry keys
- Shortcuts
In my testenvironment I’ve build a custom start menu for the user in my environment. You can do this by using the User Preferences. When you’re using Item-Level targeting, you can manage what users are getting some shortcuts. In this example I’m using Item-Level targeting with Security Groups, so when a user is member of a specific security group, he’ll receive the shortcut in his start menu.
1.) First make a new Group Polciy
2.) Go to User Configuration, Preferences, Windows Settings, Shortcuts
3.) Create a new shortcut
4.) Fill in the right path’s **picture 3**
5.) Go to the Common tab
6.) Enable “Remove this item when it is no longer applied” (note: this will change the “Action” to Replace)
7.) Enable “Item-level targeting” and click “Targeting”
8.) Select the way off targeting (note: in this example I’m using Security Group)
9.) Make the right users members of the security group
10.) Logon to your workstation and check your start menu
As you can see, based on the group membership, User01 get’s his shorcuts to the different applications. This can also be configured on the other User Preferences.
Posted in Microsoft Windows 2008 Server | No Comments »
Exchange 2007 SP1 Rollup 9 is available. You can download it here.
Update Rollup 9 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:
943073 (http://support.microsoft.com/kb/943073/ ) An image attachment appears as a red “X” when you send an RTF e-mail message from an Exchange Server 2007 organization to an external recipient
945877 (http://support.microsoft.com/kb/945877/ ) The “eseutil /k” command takes a long time to verify the checksum of transaction logs in Exchange Server 2007 Service Pack 1
947662 (http://support.microsoft.com/kb/947662/ ) The transport rule “when the Subject field or the body of the message contains text patterns” does not work accurately on an Exchange Server 2007 Service Pack 1-based computer
954739 (http://support.microsoft.com/kb/954739/ ) The Exchange Impersonation feature does not work if a cross-forest topology has only a one-way trust relationship between forests in Exchange Server 2007 Service Pack 1
957137 (http://support.microsoft.com/kb/957137/ ) The reseed process is unsuccessful on the CCR passive node after you restore one full backup and two or more differential backups to the CCR active node in Exchange Server 2007 Service Pack 1
957374 (http://support.microsoft.com/kb/957374/ ) The Microsoft Exchange Replication service on a Standby Continuous Replication (SCR) target server continually crashes when you enable SCR for a storage group on an Exchange Server 2007 Service Pack 1-based computer
959559 (http://support.microsoft.com/kb/959559/ ) Transaction log files grow unexpectedly in an Exchange Server 2007 Service Pack 1 mailbox server on a computer that is running Windows Server 2008
961124 (http://support.microsoft.com/kb/961124/ ) Some messages are stuck in the Outbox folder or the Drafts folder on a computer that is running Exchange Server 2007 Service Pack 1
961544 (http://support.microsoft.com/kb/961544/ ) Mobile users whose location is set to New Zealand cannot synchronize an exceptional occurrence after the daylight saving time (DST) update that is described in KB 951072 is installed on an Exchange 2007 Service Pack 1 Client Access server (CAS)
961551 (http://support.microsoft.com/kb/961551/ ) An error message is returned when you run the Get-Recipient command in the Exchange Management Shell that uses a Windows 7 domain controller
963679 (http://support.microsoft.com/kb/963679/ ) The Update-Recipient command does not update specified domain controller parameters when you use Identity Lifecycle Manager (ILM) 2007 to migrate mail users to mailbox users in Exchange Server 2007 Service Pack 1
967479 (http://support.microsoft.com/kb/967479/ ) Entourage clients cannot synchronize with mailboxes that are located on a computer that is running Exchange 2007 Service Pack 1 and Windows Server 2008
967525 (http://support.microsoft.com/kb/967525/ ) Error 4 is returned when you synchronize a supported list of contact properties by using Exchange ActiveSync in Exchange Server 2007 Service Pack 1
967605 (http://support.microsoft.com/kb/967605/ ) A non-delivery report (NDR) is returned when a user sends an e-mail message to an X.400 address that includes the slash field separator in Exchange Server 2007 Service Pack 1
967676 (http://support.microsoft.com/kb/967676/ ) E-mail address properties of contacts changed through Exchange Web Services (EWS) are not updated in Outlook or Outlook Web Access (OWA) in Exchange Server 2007 Service Pack 1
967739 (http://support.microsoft.com/kb/967739/ ) If a sender requests a delivery receipt in an e-mail message, a delivery status notification (DSN) message is returned that has a blank subject in the body even though the original message contains a subject in Exchange Server 2007 Service Pack 1
968081 (http://support.microsoft.com/kb/968081/ ) Monthly recurring meetings are declined if the “Schedule only during working hours” option is enabled in Exchange Server 2007 Service Pack 1
968106 (http://support.microsoft.com/kb/968106/ ) Outlook clients are directed to global catalogs from the wrong domain if you are using a split session configuration to enable Outlook clients to access their mailboxes through an RPC/HTTP proxy server in Exchange Server 2007 Service Pack 1
968111 (http://support.microsoft.com/kb/968111/ ) Event ID 4999 is logged when an administrator deletes a mailbox store on an Exchange Server 2007 Service Pack 1-based server
968205 (http://support.microsoft.com/kb/968205/ ) The Microsoft Exchange Information Store service crashes every time that a specific database is mounted on a computer that is running Exchange Server 2007 Service Pack 1
968224 (http://support.microsoft.com/kb/968224/ ) You still receive unexpected error messages when you run the Test-OwaConnectivity command or the Test-ActiveSyncConnectivity command after you apply hotfix KB954213 on an Exchange 2007 Service Pack 1-based server
968322 (http://support.microsoft.com/kb/968322/ ) An HTTP 500 error message is returned when you send a message that has a large attachment by using Outlook Web Access (OWA) with S/MIME installed in Exchange Server 2007 Service Pack 1
968350 (http://support.microsoft.com/kb/968350/ ) When you change the location field of a recurring calendar item to empty in Exchange Server 2007 Service Pack 1, the location field is set to the default value of the recurring series if this recurring item is synchronized on a Windows Mobile device
968621 (http://support.microsoft.com/kb/968621/ ) The Microsoft Exchange Information Store service crashes when you use a Data Protection Manager (DPM) 2007 server to perform a snapshot backup for an Exchange Server 2007 Service Pack 1 server
968626 (http://support.microsoft.com/kb/968626/ ) Event ID 1009 is logged when you use an application to access a shared mailbox by using the POP3 protocol in Exchange Server 2007 Service Pack 1
968651 (http://support.microsoft.com/kb/968651/ ) Exchange Server 2007 Service Pack 1 servers continue to contact a domain controller even after you exclude it by using the Set-ExchangeServer command
968715 (http://support.microsoft.com/kb/968715/ ) Both public logons and private logons that connect to a Client Access server (CAS) proxy are processed as private logons on an Exchange Server 2007 Service Pack 1-based server
969054 (http://support.microsoft.com/kb/969054/ ) Error message after an Exchange Server 2007 Service Pack 1 user replies to a message that has more than 300 recipients in Outlook Web Access (OWA): “Microsoft Exchange issued an unexpected response (500)”
969089 (http://support.microsoft.com/kb/969089/ ) Some databases are not mounted on the target server after you use the Move-ClusteredMailboxServer command to transfer a clustered mailbox server (CMS) to an available passive cluster node in Exchange Server 2007 Service Pack 1
969129 (http://support.microsoft.com/kb/969129/ ) HTML e-mail messages that have a charset META tag that differs from the MIME charset tag are garbled when they are processed through disclaimer rules in Exchange Server 2007 Service Pack 1
969324 (http://support.microsoft.com/kb/969324/ ) Outlook crashes when you try to use Outlook to view e-mail messages that are arranged by subject in Exchange Server 2007 Service Pack 1
969436 (http://support.microsoft.com/kb/969436/ ) You cannot log on to a hidden mailbox by using Base64 authentication for IMAP4 or for POP3 in an Exchange Server 2007 Service Pack 1 environment
969838 (http://support.microsoft.com/kb/969838/ ) An error message is returned when a user tries to change a recurring appointment in Office Outlook Web Access that was created in Outlook 2007 in Exchange Server 2007 Service Pack 1
969911 (http://support.microsoft.com/kb/969911/ ) Mailboxes do not follow E-mail Lifecycle (ELC) configuration or storage limitation policies in Exchange Server 2007 Service Pack 1
969943 (http://support.microsoft.com/kb/969943/ ) Memory leaks occur in the Powershell.exe process when you run the Get-MailboxStatistics command and the Get-PublicFolderStatistics command in Exchange Server 2007 Service Pack 1
969969 (http://support.microsoft.com/kb/969969/ ) Error message when an Exchange Server 2007 Service Pack 1 user tries to delete a calendar item in OWA: “Outlook Web Access has encountered a Web browsing error”
970028 (http://support.microsoft.com/kb/970028/ ) The Store.exe process crashes when you use a WebDAV application to connect to Exchange Server 2007 Service Pack 1
970086 (http://support.microsoft.com/kb/970086/ ) Exchange Server 2007 Service Pack 1 crashes when the Extensible Storage Engine (ESE) version store is out of memory on a computer that is running Windows Server 2008
970277 (http://support.microsoft.com/kb/970277/ ) The System Attendant (SA) resource is not brought online or offline during a failover in an Exchange 2007 Service Pack 1 cluster environment
970444 (http://support.microsoft.com/kb/970444/ ) A move operation between an Exchange Server 2003-based server and an Exchange Server 2007 Service Pack 1-based server fails if the SimpleDisplayName attribute of a mailbox in the Exchange Server 2003-based server contains a single quotation mark
970515 (http://support.microsoft.com/kb/970515/ ) You receive an error message when you try to use the “New-Mailbox” command to create more than 1000 users who have the same “mailNickname” attribute (alias) in Exchange Server 2007 Service Pack 1
970526 (http://support.microsoft.com/kb/970526/ ) The EdgeTransport.exe process on a computer that is running Exchange Server 2007 Service Pack 1 crashes when a MIME message that contains iCAL items for a recurring meeting has more than 999 occurrences
970725 (http://support.microsoft.com/kb/970725/ ) Public folder replication messages stay in the local delivery queue and cause an Exchange Server 2007 Service Pack 1 database to grow quickly
970993 (http://support.microsoft.com/kb/970993/ ) Error message when a user tries to perform an address book search by using Outlook Web Access in an Exchange Server 2007 Service Pack 1 environment: “The item that you attempted to access appears to be corrupted and cannot be accessed.”
Posted in Microsoft Exchange 2007 Server | No Comments »
If you want to learn all the ins en outs about PowerShell….this is your chance! Download the free PowerShell eBook Mastering PowerShell
Posted in Microsoft Exchange 2007 Scripts | No Comments »
An easy way to manage your windows event viewer is to use PowerShell. With some simple commands you can open all the events. Let’s have a look on that….
Get-EventLog *
(gives an overview of all the available event sources)
Get-EventLog -LogName”DNS Server”
(gives all the event logs in the DNS server log)
Get-EventLog -LogName “DNS Server” -Newest 10
(gives the newest 10 event logs in the DNS server log)
When you put the following commands into a PS1 file and schedule it on a specific server, you’ll receive the event logs in an e-mail! 
(in this example you’ll receive an e-mail from eventviewer@e2k10.local with the 10 newest event logs)
—————————————————————————
$body = Get-EventLog -LogName “dns server” -Newest 10 | out-string
$From = “eventviewer@e2k10.local”
$to = “administrator@e2k10.local”
$server = “srv-exc2010.e2k10.local”
$subject = “Event Viewer – srv-exc2010.e2k10.local”
$msg = new-object System.Net.Mail.MailMessage $From, $to, $subject, $body
$client = new-object System.Net.Mail.SmtpClient $Server
$Client.Send($msg)
—————————————————————————
Posted in Microsoft Exchange 2007 Scripts | No Comments »
In my virtual environment at home i’m using VMware Workstation on the host. Today i’ve installed an new Terminal Server 2003 environment with RES PowerFuse and RES Wisdom. All the users have mandatory profiles, published with RES PowerFuse. When I login with a user, there’s a copy of the mandatory profile in the %systemroot%\Documents and Settings. In my TSpolicy i’ve enabled the option “delete cached copy of roaming profiles”, so all the profiles should disappear when the users logoff.
All the userprofiles are still there when the user logoff, included only one directory and one file…hgfs.dat. The file hgfs.dat comes from VMware shared folder feature. The files is created in the profile of the first user that logs on. The file handle is kept open and therefore you might get more profile folders for the same user.
I’ve fixed it with the following VMware (VMware FAQ1317) article.
1.) Open regedit on your Terminal Server
2.) Locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
3.) Edit the key ProviderOrder
4.) Remove vmhgfs
5.) Close regedit
6.) Reboot your Terminal Server
Posted in Microsoft Windows 2003 Server | 3 Comments »
