Thursday, April 28, 2011
Monday, July 19, 2010
How to customize a default user profile in Windows 7
http://support.microsoft.com/kb/973289/en-us
To customize a default user profile or a mandatory user profile, you must first...To customize a default user profile or a mandatory user profile, you must first customize the default user profile. Then, the default user profile can be copied to the appropriate shared folder to make that user profile either the default user profile or a mandatory user profile.
When the default user profile is customized in the manner that is described in this article, it reconstructs the source profile in a format that is appropriate for use by multiple users. This is the only supported method of customizing the default user profile for the Windows operating system. If you try to use other methods to customize the default user profile, it may result in extraneous information being included in this new default user profile. Such extraneous information could lead to serious problems with applications and system stability.
Back to the top
MORE INFORMATIONHow to customize a default user profile in Windows 7 and in Windows Server 2008...How to customize a default user profile in Windows 7 and in Windows Server 2008 R2
You can customize the default user profile by using the following Copy Profile parameter in the Unattend.xml answer file that is passed to the Sysprep.exe tool:
Microsoft-Windows-Shell-Setup\CopyProfile
To do this, follow these steps:
Use the local administrator account or an local account that has administrative privileges to log on to the computer.
Note You cannot use a domain account for this process. This is because when sysprep is executed it deletes that profile and the copying of the profile occurs during specialize phase on first bootup of the image. If you use a domain account the copy profile process will copy the profile with the latest time/date stamp.
Configure the settings that you want to use in the profile. This includes desktop settings, favorites, and Start menu options.
Create an Unattend.xml file that contains the Copy Profile parameter. By using this Copy Profile parameter, the settings of the user who is currently logged on are copied to the default user profile. This parameter must be set to "true" in the specialize pass. For example, the parameter must be as follows:
true
You can use the Windows System Image Manager tool to create the Unattend.xml file. The Windows System Image Manager tool is included as part of the Windows Automated Installation Kit (Windows AIK). For more information about Windows AIK, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/dd349343.aspx (http://technet.microsoft.com/en-us/library/dd349343.aspx)
For more information on how to create an answer file, see the Help information that is included with Windows AIK and then visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/dd744394(WS.10).aspx (http://technet.microsoft.com/en-us/library/dd744394(WS.10).aspx)
At a command prompt, type the following command, and then press ENTER:
sysprep.exe /oobe /reboot /generalize /unattend:c:\answerfile\unattend.xml
Sysprep.exe is located in the %systemdrive%\Windows\System32\sysprep directory. For more information about Sysprep, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc766049.aspx (http://technet.microsoft.com/en-us/library/cc766049.aspx)
Note You must use the /generalize switch so that the Copy Profile parameter can be used. The /unattend option is used to point to the desired Unattend.xml file. Therefore, in this example, the Unattend.xml file is located in the c:\answerfile folder.
Back to the top
How to turn the default user profile into a network default user profile in Windows 7 and in Windows Server 2008 R2
Log on to the computer that has the customized default user profile by using an account that has administrative privileges.
Use the Run command to connect to the NETLOGON shared folder of a domain controller. For example, the path resembles the following:
\\\NETLOGON
Create a new folder in the NETLOGON shared folder, and name it Default User.v2.
Click Start from the Start menu, right-click Computer, click Properties, and then click Advanced system settings.
Under User Profiles, click Settings. The User Profiles dialog box shows a list of profiles that are stored on the computer.
Select Default Profile, and then click Copy To.
In the Copy profile to text box, type the network path of the Windows 7 default user profile folder that you created in step 3. For example, type the following path:
\\\NETLOGON\Default User.v2
Under Permitted to use, click Change, type the name Everyone, and then click OK.
Click OK to start to copy the profile.
Log off the computer when the copying process is completed.
Back to the top
How to turn the default user profile into a mandatory user profile in Windows 7 and in Windows Server 2008 R2
You can configure the default local user profile to become a mandatory profile. By doing this, you can have one central profile that is used by all users. To do this, you have to prepare the mandatory profile location, copy the local default user profile to the mandatory profile location, and then configure a user’s profile location to point to the mandatory profile.
Step 1: Prepare the mandatory profile location
On a central file server, create a new folder or use an existing folder that you use for roaming user profiles. For example, you can use the following folder name "Profiles":
\Profiles
If you are creating a new folder, share the folder by using a name that is suitable for your organization.
Note The share permissions for shared folders that contain roaming user profiles must enable Full Control permissions for the Authenticated Users group. The share permissions for folders that are dedicated to storing mandatory user profiles should enable Read permissions for the Authenticated Users group and enable Full Control permissions for the Administrators group.
Create a new folder in the folder that is created or identified in step 1a. The name of this new folder should start with the logon name of the user account if the mandatory user profile is for a specific user. If the mandatory user profile is for more than one user, name it accordingly. For example, the following domain has a mandatory profile, and the folder name begins with the word "mandatory":
\Profiles\mandatory
Finish naming the folder by adding .v2 after the name. The example that is used in step 1c has the folder name "mandatory." Therefore, the final name of the following folder for this user is "mandatory.v2":
\Profiles\mandatory.v2
Step 2: Copy the default user profile to the mandatory profile location
Log on to the computer that has the customized local default user profile by using an account that has administrative privileges.
Click Start from the Start menu, right-click Computer, click Properties, and then click Advanced System Settings.
Under User Profiles, click Settings. The User Profiles dialog box shows a list of profiles that are stored on the computer.
Select Default Profile, and then click Copy To.
In the Copy profile to text box, type the network path of the Windows 7 default user folder that you created in the "step 1: Prepare the mandatory profile location" section. For example, type the following path:
\\\Profiles\mandatory.v2
Under Permitted to use, click Change, type the name Everyone, and then click OK.
Click OK to start to copy the profile.
Log off the computer when the copying process is completed.
On the central file server, locate the folder that you created in the "step 1: Prepare the mandatory profile location" section."
Click Organize, and then click Folder options.
Click the View tab, click to select the Show hidden files and folders check box, click to clear the Hide extensions for known file types check box, click to clear the Hide protected operating system files check box, click Yes to dismiss the warning, and then click OK to apply the changes and close the dialog box.
Locate and right-click the NTUSER.DAT file, click Rename, change the name of the file to NTUSER.MAN, and then press ENTER.
Note Previously it was possible to copy profiles by using the System Control Panel Item. This copy to default profile option is now disabled as it could add data that made the profile unusable.
Step3: Prepare a user account
As a domain administrator, open the Active Directory Users and Computers management console from a Windows Server 2008 R2 or Windows Server 2008 computer.
Right-click the user account to which you want to apply the mandatory user profile, and then click Properties.
Click the Profile tab, type the network path that you created in the "step 1: Prepare the mandatory profile location" section in the profile path text box. However, do not add ".v2" at the end. In our example, the path would be as follows:
\\\Profiles\mandatory
Click OK, and then close the Active Directory Users and Computers management console.
The user will now use the customized mandatory user profile.
To customize a default user profile or a mandatory user profile, you must first...To customize a default user profile or a mandatory user profile, you must first customize the default user profile. Then, the default user profile can be copied to the appropriate shared folder to make that user profile either the default user profile or a mandatory user profile.
When the default user profile is customized in the manner that is described in this article, it reconstructs the source profile in a format that is appropriate for use by multiple users. This is the only supported method of customizing the default user profile for the Windows operating system. If you try to use other methods to customize the default user profile, it may result in extraneous information being included in this new default user profile. Such extraneous information could lead to serious problems with applications and system stability.
Back to the top
MORE INFORMATIONHow to customize a default user profile in Windows 7 and in Windows Server 2008...How to customize a default user profile in Windows 7 and in Windows Server 2008 R2
You can customize the default user profile by using the following Copy Profile parameter in the Unattend.xml answer file that is passed to the Sysprep.exe tool:
Microsoft-Windows-Shell-Setup\CopyProfile
To do this, follow these steps:
Use the local administrator account or an local account that has administrative privileges to log on to the computer.
Note You cannot use a domain account for this process. This is because when sysprep is executed it deletes that profile and the copying of the profile occurs during specialize phase on first bootup of the image. If you use a domain account the copy profile process will copy the profile with the latest time/date stamp.
Configure the settings that you want to use in the profile. This includes desktop settings, favorites, and Start menu options.
Create an Unattend.xml file that contains the Copy Profile parameter. By using this Copy Profile parameter, the settings of the user who is currently logged on are copied to the default user profile. This parameter must be set to "true" in the specialize pass. For example, the parameter must be as follows:
You can use the Windows System Image Manager tool to create the Unattend.xml file. The Windows System Image Manager tool is included as part of the Windows Automated Installation Kit (Windows AIK). For more information about Windows AIK, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/dd349343.aspx (http://technet.microsoft.com/en-us/library/dd349343.aspx)
For more information on how to create an answer file, see the Help information that is included with Windows AIK and then visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/dd744394(WS.10).aspx (http://technet.microsoft.com/en-us/library/dd744394(WS.10).aspx)
At a command prompt, type the following command, and then press ENTER:
sysprep.exe /oobe /reboot /generalize /unattend:c:\answerfile\unattend.xml
Sysprep.exe is located in the %systemdrive%\Windows\System32\sysprep directory. For more information about Sysprep, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc766049.aspx (http://technet.microsoft.com/en-us/library/cc766049.aspx)
Note You must use the /generalize switch so that the Copy Profile parameter can be used. The /unattend option is used to point to the desired Unattend.xml file. Therefore, in this example, the Unattend.xml file is located in the c:\answerfile folder.
Back to the top
How to turn the default user profile into a network default user profile in Windows 7 and in Windows Server 2008 R2
Log on to the computer that has the customized default user profile by using an account that has administrative privileges.
Use the Run command to connect to the NETLOGON shared folder of a domain controller. For example, the path resembles the following:
\\
Create a new folder in the NETLOGON shared folder, and name it Default User.v2.
Click Start from the Start menu, right-click Computer, click Properties, and then click Advanced system settings.
Under User Profiles, click Settings. The User Profiles dialog box shows a list of profiles that are stored on the computer.
Select Default Profile, and then click Copy To.
In the Copy profile to text box, type the network path of the Windows 7 default user profile folder that you created in step 3. For example, type the following path:
\\
Under Permitted to use, click Change, type the name Everyone, and then click OK.
Click OK to start to copy the profile.
Log off the computer when the copying process is completed.
Back to the top
How to turn the default user profile into a mandatory user profile in Windows 7 and in Windows Server 2008 R2
You can configure the default local user profile to become a mandatory profile. By doing this, you can have one central profile that is used by all users. To do this, you have to prepare the mandatory profile location, copy the local default user profile to the mandatory profile location, and then configure a user’s profile location to point to the mandatory profile.
Step 1: Prepare the mandatory profile location
On a central file server, create a new folder or use an existing folder that you use for roaming user profiles. For example, you can use the following folder name "Profiles":
\Profiles
If you are creating a new folder, share the folder by using a name that is suitable for your organization.
Note The share permissions for shared folders that contain roaming user profiles must enable Full Control permissions for the Authenticated Users group. The share permissions for folders that are dedicated to storing mandatory user profiles should enable Read permissions for the Authenticated Users group and enable Full Control permissions for the Administrators group.
Create a new folder in the folder that is created or identified in step 1a. The name of this new folder should start with the logon name of the user account if the mandatory user profile is for a specific user. If the mandatory user profile is for more than one user, name it accordingly. For example, the following domain has a mandatory profile, and the folder name begins with the word "mandatory":
\Profiles\mandatory
Finish naming the folder by adding .v2 after the name. The example that is used in step 1c has the folder name "mandatory." Therefore, the final name of the following folder for this user is "mandatory.v2":
\Profiles\mandatory.v2
Step 2: Copy the default user profile to the mandatory profile location
Log on to the computer that has the customized local default user profile by using an account that has administrative privileges.
Click Start from the Start menu, right-click Computer, click Properties, and then click Advanced System Settings.
Under User Profiles, click Settings. The User Profiles dialog box shows a list of profiles that are stored on the computer.
Select Default Profile, and then click Copy To.
In the Copy profile to text box, type the network path of the Windows 7 default user folder that you created in the "step 1: Prepare the mandatory profile location" section. For example, type the following path:
\\
Under Permitted to use, click Change, type the name Everyone, and then click OK.
Click OK to start to copy the profile.
Log off the computer when the copying process is completed.
On the central file server, locate the folder that you created in the "step 1: Prepare the mandatory profile location" section."
Click Organize, and then click Folder options.
Click the View tab, click to select the Show hidden files and folders check box, click to clear the Hide extensions for known file types check box, click to clear the Hide protected operating system files check box, click Yes to dismiss the warning, and then click OK to apply the changes and close the dialog box.
Locate and right-click the NTUSER.DAT file, click Rename, change the name of the file to NTUSER.MAN, and then press ENTER.
Note Previously it was possible to copy profiles by using the System Control Panel Item. This copy to default profile option is now disabled as it could add data that made the profile unusable.
Step3: Prepare a user account
As a domain administrator, open the Active Directory Users and Computers management console from a Windows Server 2008 R2 or Windows Server 2008 computer.
Right-click the user account to which you want to apply the mandatory user profile, and then click Properties.
Click the Profile tab, type the network path that you created in the "step 1: Prepare the mandatory profile location" section in the profile path text box. However, do not add ".v2" at the end. In our example, the path would be as follows:
\\
Click OK, and then close the Active Directory Users and Computers management console.
The user will now use the customized mandatory user profile.
Thursday, April 08, 2010
Connecting an iPhone to Exchange
Source:
http://simultaneouspancakes.com/Lessons/2009/09/10/connecting-iphone-3-x-to-exchange/
Connecting iPhone 3.x to Exchange
By Q .I originally posted instructions for configuring an iPhone 2.0 device to an Exchange server back when the iPhone 3G was originally released. While those instructions still hold for the most part, the iPhone interface has changed somewhat, so here’s an updated post with pics for connecting the iPhone 3.x OS to an Exchange server.
1.From the Home screen (unless you’ve relocated the icon) open the Settings app.
2.Click the Mail, Contacts, Calendars item in the list.
3.Click Add Account.
4.Click Microsoft Exchange at the top of the list.
5.Enter your e-mail account information.
For the Email field, enter your default e-mail address exactly as it appears on your outgoing messages. This is important: if your outgoing e-mail address is Jon.Dough@smallbizco.net, you must match it exactly. If you enter jon.dough@smallbizco.net, you may encounter issues with calendar items. You may not need to enter the Domain field, but do enter it if you know what it is. Your username and password should match what you enter to access Outlook Web Access or your network account. If you do not know this information, you will need to get it from your system administrator.
6.Once you have entered the account information, click Next. The iPhone will attempt to connect to your mail server. You may be prompted to enter the name of the mail server if it could not be found automatically. This is the same as the server you use to access Outlook Web Access. If your Outlook Web Access server is https://remote.smallbizco.net/owa, then you need to enter remote.smallbizco.net as the mail server. Then click Next.
7.If the iPhone cannot correctly validate the security certificate on your mail server (this may be the case if your Exchange server is running on Small Business Server 2003 or 2008), you will be asked what to do about the connection. If you know you have entered the correct information about your mail server, click Accept. If not, click Cancel.
8.Choose which items from the Exchange server you want to sync with your iPhone. If you already have your contacts or calendar synchronizing with another source, you may want to hold off on selecting those to avoid a potential loss of data.
9.Click Done when finished.
The iPhone will now start the initial connection to the Exchange server and synchronize the selected information.
http://simultaneouspancakes.com/Lessons/2009/09/10/connecting-iphone-3-x-to-exchange/
Connecting iPhone 3.x to Exchange
By Q .I originally posted instructions for configuring an iPhone 2.0 device to an Exchange server back when the iPhone 3G was originally released. While those instructions still hold for the most part, the iPhone interface has changed somewhat, so here’s an updated post with pics for connecting the iPhone 3.x OS to an Exchange server.
1.From the Home screen (unless you’ve relocated the icon) open the Settings app.
2.Click the Mail, Contacts, Calendars item in the list.
3.Click Add Account.
4.Click Microsoft Exchange at the top of the list.
5.Enter your e-mail account information.
For the Email field, enter your default e-mail address exactly as it appears on your outgoing messages. This is important: if your outgoing e-mail address is Jon.Dough@smallbizco.net, you must match it exactly. If you enter jon.dough@smallbizco.net, you may encounter issues with calendar items. You may not need to enter the Domain field, but do enter it if you know what it is. Your username and password should match what you enter to access Outlook Web Access or your network account. If you do not know this information, you will need to get it from your system administrator.
6.Once you have entered the account information, click Next. The iPhone will attempt to connect to your mail server. You may be prompted to enter the name of the mail server if it could not be found automatically. This is the same as the server you use to access Outlook Web Access. If your Outlook Web Access server is https://remote.smallbizco.net/owa, then you need to enter remote.smallbizco.net as the mail server. Then click Next.
7.If the iPhone cannot correctly validate the security certificate on your mail server (this may be the case if your Exchange server is running on Small Business Server 2003 or 2008), you will be asked what to do about the connection. If you know you have entered the correct information about your mail server, click Accept. If not, click Cancel.
8.Choose which items from the Exchange server you want to sync with your iPhone. If you already have your contacts or calendar synchronizing with another source, you may want to hold off on selecting those to avoid a potential loss of data.
9.Click Done when finished.
The iPhone will now start the initial connection to the Exchange server and synchronize the selected information.
Labels: Exchange03, Exchange07, iPhone
Wednesday, March 31, 2010
Media Player doesn't start in IE8 When Clicking on Links containing .avi, asf, ,wmv, mpg, mpeg,
When I moved to Win7 I noticed that any Links that contained a URL with
.wmv, mpg, mpeg, avi,
Why I didn't have a clue I did some looking and I found this answer:
>>>>>>>>>>>Microsoft Answer was. <<<<<<<<<<<<<<
To resolve this behavior, reregister the Wmpdxm.dll file.
To do this, follow these steps:
1.At a command prompt, type one of the following commands:
•%systemroot%\system32
•c:\windows\system32
2.At a command prompt, type the following command:
regsvr32.exe wmpdxm.dll
3.Start Registry Editor. Verify that the following registry key points to the correct path and file name for the (Default) value:
HKEY_CLASSES_ROOT\CLSID\{22D6F312-B0F6-11D0-94AB-0080C74C7E95}\InprocServer32
Typically, the registry key points to the following path and file name:
C:\Windows\System32\Wmpdxm.dll
>>>>>> End of Microsoft Answer <<<<<<<<
However I found that didn't work
Looking around I found a post from Charles_Flook
http://social.answers.microsoft.com/Forums/en-US/w7pictures/thread/12fd4dd3-344b-4f5e-9201-ccaf2eefae13
And he suggested this which worked.
Open up notepad.exe
past the below into notepad and save as a MediaPlayerFix.reg file and open.
(allow it to make the changes)
>>>>>>>>>> MediaPlayerFix.reg <<<<<<<<<<<<<
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.avi]
@="WMP11.AssocFile.AVI"
[HKEY_CLASSES_ROOT\.asf]
@="WMP11.AssocFile.ASF"
[HKEY_CLASSES_ROOT\.wmv]
@="WMP11.AssocFile.WMV"
[HKEY_CLASSES_ROOT\.mpg]
@="WMP11.AssocFile.MPG
[HKEY_CLASSES_ROOT\.mpeg]
@="WMP11.AssocFile.MPEG
>>>>>>>>>>>>>>>>>> End <<<<<<<<<<<<<<<
Then any links that end in the .avi, asf, ,wmv, mpg, mpeg, wiill open media Player.
Thanks Charles_Flook
.wmv, mpg, mpeg, avi,
Why I didn't have a clue I did some looking and I found this answer:
>>>>>>>>>>>Microsoft Answer was. <<<<<<<<<<<<<<
To resolve this behavior, reregister the Wmpdxm.dll file.
To do this, follow these steps:
1.At a command prompt, type one of the following commands:
•%systemroot%\system32
•c:\windows\system32
2.At a command prompt, type the following command:
regsvr32.exe wmpdxm.dll
3.Start Registry Editor. Verify that the following registry key points to the correct path and file name for the (Default) value:
HKEY_CLASSES_ROOT\CLSID\{22D6F312-B0F6-11D0-94AB-0080C74C7E95}\InprocServer32
Typically, the registry key points to the following path and file name:
C:\Windows\System32\Wmpdxm.dll
>>>>>> End of Microsoft Answer <<<<<<<<
However I found that didn't work
Looking around I found a post from Charles_Flook
http://social.answers.microsoft.com/Forums/en-US/w7pictures/thread/12fd4dd3-344b-4f5e-9201-ccaf2eefae13
And he suggested this which worked.
Open up notepad.exe
past the below into notepad and save as a MediaPlayerFix.reg file and open.
(allow it to make the changes)
>>>>>>>>>> MediaPlayerFix.reg <<<<<<<<<<<<<
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.avi]
@="WMP11.AssocFile.AVI"
[HKEY_CLASSES_ROOT\.asf]
@="WMP11.AssocFile.ASF"
[HKEY_CLASSES_ROOT\.wmv]
@="WMP11.AssocFile.WMV"
[HKEY_CLASSES_ROOT\.mpg]
@="WMP11.AssocFile.MPG
[HKEY_CLASSES_ROOT\.mpeg]
@="WMP11.AssocFile.MPEG
>>>>>>>>>>>>>>>>>> End <<<<<<<<<<<<<<<
Then any links that end in the .avi, asf, ,wmv, mpg, mpeg, wiill open media Player.
Thanks Charles_Flook
Saturday, March 06, 2010
BlackBerry Enterprise Server Express for Free SBS2008
BlackBerry Enterprise Server Express for Free
http://na.blackberry.com/eng/services/business/server/express/
Connect two people via BlackBerry® Smartphone's and ideas get bigger.
Progress happens faster. Answers get smarter. So imagine what happens when
you give a business the freedom to connect all its employees.
BlackBerry® Enterprise Server Express enables businesses of any size to
quickly and easily get started with the BlackBerry solution. It provides
advanced BlackBerry Smartphone features with no additional software or user
license fees, and works with any Internet-enabled BlackBerry data plan or a
BlackBerry enterprise data plan.
System Requirements
http://na.blackberry.com/eng/services/business/server/express/RIM707_System_Requirements.pdf
http://na.blackberry.com/eng/services/business/server/express/
Connect two people via BlackBerry® Smartphone's and ideas get bigger.
Progress happens faster. Answers get smarter. So imagine what happens when
you give a business the freedom to connect all its employees.
BlackBerry® Enterprise Server Express enables businesses of any size to
quickly and easily get started with the BlackBerry solution. It provides
advanced BlackBerry Smartphone features with no additional software or user
license fees, and works with any Internet-enabled BlackBerry data plan or a
BlackBerry enterprise data plan.
System Requirements
http://na.blackberry.com/eng/services/business/server/express/RIM707_System_Requirements.pdf
Labels: BlackBerry, Exchange07, SBS2008
Wednesday, February 10, 2010
TIP: Install Basic Apps easily - www.ninite.com
Someone pointed this site out to me looks really promising:
www.NiNite.com
Install
Adobe
Java
Flash
and other needed apps
with one click.
www.NiNite.com
Install
Adobe
Java
Flash
and other needed apps
with one click.
Can't see Drive mapings in SBS2008 on XP Systems
I don't know if this a duplicat post of mine
However if you've set up SBS2008 for Drive mapping in the login scripts
and you still can't get drive mappings.
It's probably because the client side extentions are not installed on the XP system and it needs "ALL" the Updates
First go to updates.microsoft.com and update the System
and then
Group Policy Preference Client Side Extensions for Windows XP (KB943729)
http://download.microsoft.com/download/f/e/b/feb2da1e-3611-452a-b134-1ddbe5567e5f/Windows-KB943729-x86-ENU.exe
However if you've set up SBS2008 for Drive mapping in the login scripts
and you still can't get drive mappings.
It's probably because the client side extentions are not installed on the XP system and it needs "ALL" the Updates
First go to updates.microsoft.com and update the System
and then
Group Policy Preference Client Side Extensions for Windows XP (KB943729)
http://download.microsoft.com/download/f/e/b/feb2da1e-3611-452a-b134-1ddbe5567e5f/Windows-KB943729-x86-ENU.exe
Friday, January 29, 2010
Cannot See \\Server when VPN into a SBS2008 Server
From http://nicholas.piasecki.name/blog/2009/06/getting-wins-like-computer-name-resolution-over-vpn-in-sbs-2008/
Getting WINS-like computer name resolution over VPN in SBS 2008
by Nicholas Piasecki on June 13th, 2009
So this week concluded several sleepless nights and much heartburn as I migrated Skiviez’s SBS 2003 machine (running as our domain controller and our mail server) to SBS 2008. As far as things go, it went relatively smoothly, and the remainder of the week was dealing with lots of small niceties that I had forgotten that I had set up on the 2003 server that I now needed to set up once again.
One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as \\COMPUTER-NAME\SHARE-NAME; for example, \\CYRUS\Pickup Holding, because for some reason some of the older servers are named after my boss’s dead cats.
When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when \\CYRUS\Pickup Holding failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding would work fine. This was super annoying.
The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008 finally retires this ancient technology by default, however, so I had two choices: I could either install the WINS server role on SBS 2008, or I could just figure out how to get the 015 DNS Domain Name option from DHCP to relay through the VPN connection.
I chose the latter option, since it’s certainly less confusing to be able to say to someone in the future “we don’t use WINS, DNS does everything.” So here’s how to do it:
1.On the SBS 2008 server, click Start > Administrative Tools > Routing and Remote Access.
2.In the tree view, drill down past the server name to IPV4 > General. Right-click the General option and choose “New Routing Protocol” and choose DHCP Relay Agent.
3.Now right-click the newly appended “DHCP Relay Agent” node and choose Properties. Add the IP address of your DHCP server (which is probably your SBS server itself), and click OK. Then click it again and choose “New Interface” and add the “Internal” interface.
4.Now if you connect through VPN, an ipconfig /all should show your domain name as a “Connection-specific DNS suffix” and pinging machines by their suffix-less computer names should work. (If it doesn’t, make sure your DHCP server is using that 015 DNS Domain Name option, which the SBS 2008 wizards set up by default.)
Getting WINS-like computer name resolution over VPN in SBS 2008
by Nicholas Piasecki on June 13th, 2009
So this week concluded several sleepless nights and much heartburn as I migrated Skiviez’s SBS 2003 machine (running as our domain controller and our mail server) to SBS 2008. As far as things go, it went relatively smoothly, and the remainder of the week was dealing with lots of small niceties that I had forgotten that I had set up on the 2003 server that I now needed to set up once again.
One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as \\COMPUTER-NAME\SHARE-NAME; for example, \\CYRUS\Pickup Holding, because for some reason some of the older servers are named after my boss’s dead cats.
When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when \\CYRUS\Pickup Holding failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding would work fine. This was super annoying.
The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008 finally retires this ancient technology by default, however, so I had two choices: I could either install the WINS server role on SBS 2008, or I could just figure out how to get the 015 DNS Domain Name option from DHCP to relay through the VPN connection.
I chose the latter option, since it’s certainly less confusing to be able to say to someone in the future “we don’t use WINS, DNS does everything.” So here’s how to do it:
1.On the SBS 2008 server, click Start > Administrative Tools > Routing and Remote Access.
2.In the tree view, drill down past the server name to IPV4 > General. Right-click the General option and choose “New Routing Protocol” and choose DHCP Relay Agent.
3.Now right-click the newly appended “DHCP Relay Agent” node and choose Properties. Add the IP address of your DHCP server (which is probably your SBS server itself), and click OK. Then click it again and choose “New Interface” and add the “Internal” interface.
4.Now if you connect through VPN, an ipconfig /all should show your domain name as a “Connection-specific DNS suffix” and pinging machines by their suffix-less computer names should work. (If it doesn’t, make sure your DHCP server is using that 015 DNS Domain Name option, which the SBS 2008 wizards set up by default.)
Thursday, January 28, 2010
SBS 2008 Outlook Pop Ups and Continuous Logon Prompts
SBS 2008 Outlook Pop Ups and Continuous Logon Prompts
http://wintivity.wigital.net/sbs/exchange-2007-sp1-update-rollup-9-fix-outlook-pop-up-sbs-2008/
SYMPTOM: for client workstations, when Outlook is launched, all users are continuously prompted for logon credentials in order to authenticate with Exchange even though they are properly authenticated on the domain. Authentication is in the Intranet Zone. Active Directory is fully functional and integrated with Exchange.
Exchange 2007 SP 1 Update Rollup 9
The resolution to restoring Exchange authentication communication with SBS 2008 Active Directory has been, in all cases, to download and install Exchange 2007 SP1 Update Rollup 9
Here are issues we’re aware of when installing the Update Rollup 9 for Exchange.
1.When installing Exchange 2007 Sp1 Update Rollup 9 on Small Business Server 2008 it is advisable to open the command prompt and install the update using RunAs and Administrator credentials. Update Rollup 9 has failed on SBS Installations WIGITAL has attempted unless initially launched in this manner. Navigating to the path where the update package is, and launching the installer using RunAs from the command line seems to solve some UAC (User Account Control) issues.
2.You may see the following Event IDs when installing this Update Rollup: Event ID 1024, Event ID 1603, Event ID 11321. Details follow….
Log Name: Application
Source: MsiInstaller
Date: 1/11/2010 1:22:21 PM
Event ID: 1024
Task Category: None
Level: Error
Keywords: Classic
User: DOMAIN\administrator
Computer: SBS2008-SERVER.DOMAIN.local
Description:
Product: Microsoft Exchange Server - Update 'Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162) 8.1.393.1' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
as well as Event ID 11321
Log Name: Application
Source: MsiInstaller
Date: 1/11/2010 1:13:04 PM
Event ID: 11321
Task Category: None
Level: Error
Keywords: Classic
User: DOMAIN\Administrator
Computer: SBS2008-SERVER.DOMAIN.local
Description:
Product: Microsoft Exchange Server -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Program Files\Microsoft\Exchange Server\RelNotes.htm.
NOTE: For more information about errors, Exchange Server 2007 SP1 Update Rollup 9 creates a log file here:
C:\Users\Administrator.DOMAIN\AppData\Local\Temp\3\MSIec215.LOG
Review the LOG to determine a course of action if you experience errors during your install.
To remedy the 11321 error ( which we’ve seen every time we’ve installed Update Rollup 9 ):
•Open Explorer
•Go to C:\Program Files\Microsoft\Exchange Server\RelNotes.htm
•Change the permissions on this file to allow the current Administrator FULL CONTROL
•Apply the changes
•Restart Update Rollup 9 using RunAs from the Command Line
Oddly enough, the installers permissible access to RelNotes.htm has ended more than one installation prematurely
http://wintivity.wigital.net/sbs/exchange-2007-sp1-update-rollup-9-fix-outlook-pop-up-sbs-2008/
SYMPTOM: for client workstations, when Outlook is launched, all users are continuously prompted for logon credentials in order to authenticate with Exchange even though they are properly authenticated on the domain. Authentication is in the Intranet Zone. Active Directory is fully functional and integrated with Exchange.
Exchange 2007 SP 1 Update Rollup 9
The resolution to restoring Exchange authentication communication with SBS 2008 Active Directory has been, in all cases, to download and install Exchange 2007 SP1 Update Rollup 9
Here are issues we’re aware of when installing the Update Rollup 9 for Exchange.
1.When installing Exchange 2007 Sp1 Update Rollup 9 on Small Business Server 2008 it is advisable to open the command prompt and install the update using RunAs and Administrator credentials. Update Rollup 9 has failed on SBS Installations WIGITAL has attempted unless initially launched in this manner. Navigating to the path where the update package is, and launching the installer using RunAs from the command line seems to solve some UAC (User Account Control) issues.
2.You may see the following Event IDs when installing this Update Rollup: Event ID 1024, Event ID 1603, Event ID 11321. Details follow….
Log Name: Application
Source: MsiInstaller
Date: 1/11/2010 1:22:21 PM
Event ID: 1024
Task Category: None
Level: Error
Keywords: Classic
User: DOMAIN\administrator
Computer: SBS2008-SERVER.DOMAIN.local
Description:
Product: Microsoft Exchange Server - Update 'Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162) 8.1.393.1' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
as well as Event ID 11321
Log Name: Application
Source: MsiInstaller
Date: 1/11/2010 1:13:04 PM
Event ID: 11321
Task Category: None
Level: Error
Keywords: Classic
User: DOMAIN\Administrator
Computer: SBS2008-SERVER.DOMAIN.local
Description:
Product: Microsoft Exchange Server -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Program Files\Microsoft\Exchange Server\RelNotes.htm.
NOTE: For more information about errors, Exchange Server 2007 SP1 Update Rollup 9 creates a log file here:
C:\Users\Administrator.DOMAIN\AppData\Local\Temp\3\MSIec215.LOG
Review the LOG to determine a course of action if you experience errors during your install.
To remedy the 11321 error ( which we’ve seen every time we’ve installed Update Rollup 9 ):
•Open Explorer
•Go to C:\Program Files\Microsoft\Exchange Server\RelNotes.htm
•Change the permissions on this file to allow the current Administrator FULL CONTROL
•Apply the changes
•Restart Update Rollup 9 using RunAs from the Command Line
Oddly enough, the installers permissible access to RelNotes.htm has ended more than one installation prematurely
You receive a ".pst is not compatible" error message when you open an Outlook 2003 or Outlook 2007 .pst file in earlier versions of Outlook
You receive a ".pst is not compatible" error message when you open an Outlook 2003 or Outlook 2007 .pst file in earlier versions of Outlook
http://support.microsoft.com/kb/839109
When you use a version of Outlook that is earlier than Microsoft Office Outlook 2003, you may experience the following problem. If you to try to open or to import a personal folder file (.pst) that contains information that was exported from Microsoft Office Outlook 2003 or from Microsoft Office Outlook 2007, you may receive the following error message:
The file file_name.pst is not compatible with this version of the Personal Folders information service.
Contact your Administrator.
This problem occurs when the information in the .pst file was exported from Outl...This problem occurs when the information in the .pst file was exported from Outlook 2003 or from Outlook 2007 by using the Import and Export Wizard. Outlook 2003 and Outlook 2007 use the Unicode format to export information to a .pst file. Earlier versions of Outlook cannot open or import Unicode-formatted .pst files. Earlier versions of Outlook can open only .pst files that are formatted in American National Standards Institute (ANSI) format
To work around this problem, copy the contents of the Outlook 2003 or Outlook 20...To work around this problem, copy the contents of the Outlook 2003 or Outlook 2007 .pst file to a .pst file that has not been converted to the Outlook 2003 or Outlook 2007 Unicode format.
To copy information from a Unicode-formatted .pst file to an ANSI-formatted .pst file in Outlook 2003 or in Outlook 2007, follow these steps.
Note To follow these steps, you must use a .pst file from an earlier version of Outlook.
Start Outlook.
On the File menu, click Data File Management, and then click Add.
Click Outlook 97-2002 Personal Folders File (PST).
Click OK.
Click OK to accept the default name, and then click OK again.
Outlook 2003 now creates a new .pst file that is based on the earlier .pst file and maintains the ANSI formatting for that .pst file.
Click Close.
At the bottom of the navigation pane, click Folder List.
In the navigation pane, you now see the new .pst file.
Drag the information from your existing Outlook 2003 or Outlook 2007 folders to the new .pst file. You may also use the Import and Export Wizard on the File menu to move the information from your existing Outlook 2003 or Outlook 2007 folders to the new .pst file.
In the navigation pane, right-click the new .pst file, and then click Close "file_name".
Note E-mail messages or other items that contain Unicode characters will not be copied to the new .pst file.
http://support.microsoft.com/kb/839109
When you use a version of Outlook that is earlier than Microsoft Office Outlook 2003, you may experience the following problem. If you to try to open or to import a personal folder file (.pst) that contains information that was exported from Microsoft Office Outlook 2003 or from Microsoft Office Outlook 2007, you may receive the following error message:
The file file_name.pst is not compatible with this version of the Personal Folders information service.
Contact your Administrator.
This problem occurs when the information in the .pst file was exported from Outl...This problem occurs when the information in the .pst file was exported from Outlook 2003 or from Outlook 2007 by using the Import and Export Wizard. Outlook 2003 and Outlook 2007 use the Unicode format to export information to a .pst file. Earlier versions of Outlook cannot open or import Unicode-formatted .pst files. Earlier versions of Outlook can open only .pst files that are formatted in American National Standards Institute (ANSI) format
To work around this problem, copy the contents of the Outlook 2003 or Outlook 20...To work around this problem, copy the contents of the Outlook 2003 or Outlook 2007 .pst file to a .pst file that has not been converted to the Outlook 2003 or Outlook 2007 Unicode format.
To copy information from a Unicode-formatted .pst file to an ANSI-formatted .pst file in Outlook 2003 or in Outlook 2007, follow these steps.
Note To follow these steps, you must use a .pst file from an earlier version of Outlook.
Start Outlook.
On the File menu, click Data File Management, and then click Add.
Click Outlook 97-2002 Personal Folders File (PST).
Click OK.
Click OK to accept the default name, and then click OK again.
Outlook 2003 now creates a new .pst file that is based on the earlier .pst file and maintains the ANSI formatting for that .pst file.
Click Close.
At the bottom of the navigation pane, click Folder List.
In the navigation pane, you now see the new .pst file.
Drag the information from your existing Outlook 2003 or Outlook 2007 folders to the new .pst file. You may also use the Import and Export Wizard on the File menu to move the information from your existing Outlook 2003 or Outlook 2007 folders to the new .pst file.
In the navigation pane, right-click the new .pst file, and then click Close "file_name".
Note E-mail messages or other items that contain Unicode characters will not be copied to the new .pst file.
Folder Sync Still Grabbing Old Sync Folder
If you have an Issue where the PC is still grabbing an Old offline folder sync and the offline path dosn't exist anymore!
How to re-initialize the offline files cache and database
http://support.microsoft.com/kb/230738
The Offline Files (CSC or Client Side Caching) cache and database has a built-in capability to restart if its contents are suspected of being corrupted. If corruption is suspected, the Synchronization Wizard may return the following error message:
Unable to merge offline changes on \\server_name\share_name. The parameter is incorrect.
MORE INFORMATION
Method 1
The Offline Files cache is a folder structure located in the %SystemRoot%\CSC folder, which is hidden by default. The CSC folder, and any files and subfolders it contains, should not be modified directly; doing so can result in data loss and a complete breakdown of Offline Files functionality.
If you suspect corruption in the database, then the files should be deleted using the Offline Files viewer. After the files are deleted out of the Offline Files viewer, a synchronization of files may then be forced using Synchronization Manager. If the cache still does not appear to function correctly, an Offline Files reset can be performed using the following procedure:
1. In Folder Options, on the Offline Files tab, press CTRL+SHIFT, and then click Delete Files. The following message appears:
The Offline Files cache on the local computer will be re-initialized. Any changes that have not been synchronized with computers on the network will be lost. Any files or folders made available offline will no longer be available offline. A computer restart is required.
Do you wish to re-initialize the cache?
2. Click Yes two times to restart the computer.
Method 2
Use Registry Editor
If you cannot access the Offline Files tab, use this method to reinitialize the Offline Files (CSC) cache on the system by modifying the registry. Use this method also to reinitialize the offline files database/client-side cache on multiple systems. Add the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\NetCache
Key Name: FormatDatabase
Key Type: DWORD
Key Value: 1
Note The actual value of the registry key is ignored. This registry change requires a restart. When the computer is restarting, the shell will reinitialize the CSC cache, and then delete the registry key if the registry entry exists.
Warning All cache files are deleted and unsynchronized data is lost.
Use Reg.exe
You can also automate the process of setting this registry value by using the Reg.exe command line editor. To do this, type the following command in the Reg.exe window:
REG.EXE. REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\NetCache" /v FormatDatabase /t REG_DWORD /d 1 /f
Note For specific steps to re-initialize the offline files cache and database in Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:
942974 http://support.microsoft.com/kb/942974/
On a Windows Vista-based client computer, you can still access offline files even though the file server is removed from the network
Russ
How to re-initialize the offline files cache and database
http://support.microsoft.com/kb/230738
The Offline Files (CSC or Client Side Caching) cache and database has a built-in capability to restart if its contents are suspected of being corrupted. If corruption is suspected, the Synchronization Wizard may return the following error message:
Unable to merge offline changes on \\server_name\share_name. The parameter is incorrect.
MORE INFORMATION
Method 1
The Offline Files cache is a folder structure located in the %SystemRoot%\CSC folder, which is hidden by default. The CSC folder, and any files and subfolders it contains, should not be modified directly; doing so can result in data loss and a complete breakdown of Offline Files functionality.
If you suspect corruption in the database, then the files should be deleted using the Offline Files viewer. After the files are deleted out of the Offline Files viewer, a synchronization of files may then be forced using Synchronization Manager. If the cache still does not appear to function correctly, an Offline Files reset can be performed using the following procedure:
1. In Folder Options, on the Offline Files tab, press CTRL+SHIFT, and then click Delete Files. The following message appears:
The Offline Files cache on the local computer will be re-initialized. Any changes that have not been synchronized with computers on the network will be lost. Any files or folders made available offline will no longer be available offline. A computer restart is required.
Do you wish to re-initialize the cache?
2. Click Yes two times to restart the computer.
Method 2
Use Registry Editor
If you cannot access the Offline Files tab, use this method to reinitialize the Offline Files (CSC) cache on the system by modifying the registry. Use this method also to reinitialize the offline files database/client-side cache on multiple systems. Add the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\NetCache
Key Name: FormatDatabase
Key Type: DWORD
Key Value: 1
Note The actual value of the registry key is ignored. This registry change requires a restart. When the computer is restarting, the shell will reinitialize the CSC cache, and then delete the registry key if the registry entry exists.
Warning All cache files are deleted and unsynchronized data is lost.
Use Reg.exe
You can also automate the process of setting this registry value by using the Reg.exe command line editor. To do this, type the following command in the Reg.exe window:
REG.EXE. REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\NetCache" /v FormatDatabase /t REG_DWORD /d 1 /f
Note For specific steps to re-initialize the offline files cache and database in Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:
942974 http://support.microsoft.com/kb/942974/
On a Windows Vista-based client computer, you can still access offline files even though the file server is removed from the network
Russ
Friday, January 22, 2010
Unable to login to companyweb from SBS server console
This is an old issue but I still run into it so I'm blogging it.
Unable to login to companyweb from SBS server console
you get prompted for a password and even though you enter the correct credentials it gives you an error
Microsoft post found on (They have a fix it button on there.)
http://support.microsoft.com/kb/896861
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:
HTTP 401.1 - Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
Additionally, an event message that resembles the following event message is logged in the Security Event log. This event message includes some strange characters in the value for the Logon Process entry:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: Computer_Name
Description: Logon Failure:
Reason: An error occurred during logon
User Name: User_Name
Domain: Domain_Name
Logon Type: 3
Logon Process: Ðùº
Authentication Package: NTLM
Workstation Name: Computer_Name
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: IP_Address
Source Port: Port_Number
Note Sometimes, the strange characters that appear in this event message may resemble the following characters:
Ðù²
You may also receive an error message that resembles the following when you try to debug a Microsoft ASP.NET project in Microsoft Visual Studio 2003:
Error while trying to run project: Unable to start debugging on the web server. You do not have permissions to debug the server.
Verify that you are a member of the 'Debugger Users' group on the server.
Note The word "Web" is incorrectly capitalized in this error message.
Calls that are made from a Web service do not result in an HTTP 401 message in the IIS logs. An HTTP 401 message may be noted in the Description section of an Error event for an application that uses a Web service. For example, this behavior may occur for Microsoft Commerce Server 2002. If this behavior occurs, it is a symptom of a change that is made by Microsoft Windows Server 2003 Service Pack 1 (SP1) and the loopback check security feature.
CAUSE This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Mi...This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.
WORKAROUNDImportant This section, method, or task contains steps that tell you how to modi...Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
There are two methods to work around this issue, use one of the following methods, as appropriate for your situation.
Method 1: Disable the loopback check
The first method is to disable the loopback check by setting the DisableLoopbackCheck registry key.
To set the DisableLoopbackCheck registry key yourself, follow these steps:
Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor, and then restart your computer.
Method 2: Specify host names
To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:
Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Right-click MSV1_0, point to New, and then click Multi-String Value.
Type BackConnectionHostNames, and then press ENTER.
Right-click BackConnectionHostNames, and then click Modify.
In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
Quit Registry Editor, and then restart the IISAdmin service.
Back to the top
Unable to login to companyweb from SBS server console
you get prompted for a password and even though you enter the correct credentials it gives you an error
Microsoft post found on (They have a fix it button on there.)
http://support.microsoft.com/kb/896861
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:
HTTP 401.1 - Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
Additionally, an event message that resembles the following event message is logged in the Security Event log. This event message includes some strange characters in the value for the Logon Process entry:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: Computer_Name
Description: Logon Failure:
Reason: An error occurred during logon
User Name: User_Name
Domain: Domain_Name
Logon Type: 3
Logon Process: Ðùº
Authentication Package: NTLM
Workstation Name: Computer_Name
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: IP_Address
Source Port: Port_Number
Note Sometimes, the strange characters that appear in this event message may resemble the following characters:
Ðù²
You may also receive an error message that resembles the following when you try to debug a Microsoft ASP.NET project in Microsoft Visual Studio 2003:
Error while trying to run project: Unable to start debugging on the web server. You do not have permissions to debug the server.
Verify that you are a member of the 'Debugger Users' group on the server.
Note The word "Web" is incorrectly capitalized in this error message.
Calls that are made from a Web service do not result in an HTTP 401 message in the IIS logs. An HTTP 401 message may be noted in the Description section of an Error event for an application that uses a Web service. For example, this behavior may occur for Microsoft Commerce Server 2002. If this behavior occurs, it is a symptom of a change that is made by Microsoft Windows Server 2003 Service Pack 1 (SP1) and the loopback check security feature.
CAUSE This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Mi...This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.
WORKAROUNDImportant This section, method, or task contains steps that tell you how to modi...Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
There are two methods to work around this issue, use one of the following methods, as appropriate for your situation.
Method 1: Disable the loopback check
The first method is to disable the loopback check by setting the DisableLoopbackCheck registry key.
To set the DisableLoopbackCheck registry key yourself, follow these steps:
Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor, and then restart your computer.
Method 2: Specify host names
To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:
Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Right-click MSV1_0, point to New, and then click Multi-String Value.
Type BackConnectionHostNames, and then press ENTER.
Right-click BackConnectionHostNames, and then click Modify.
In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
Quit Registry Editor, and then restart the IISAdmin service.
Back to the top
Thursday, December 31, 2009
How to install Exchange SP2 on SBS2008 (Exchange 2007)
Microsoft Exchange Server 2007 SP2 Installation Tool for Windows SBS 2008
http://www.microsoft.com/downloads/details.aspx?FamilyID=ffd2fe61-9278-489e-9b96-3816394c9cb6&displayLang=en
If you didn’t have this tool you’d have to do this.
Download Exchange 2007 SP2
http://www.microsoft.com/downloads/details.aspx?FamilyID=4C4BD2A3-5E50-42B0-8BBB-2CC9AFE3216A&displaylang=en
How to install Exchange 2007 SP2 on SBS2008 without tool
http://support.microsoft.com/default.aspx?scid=kb;EN-US;973862
http://www.microsoft.com/downloads/details.aspx?FamilyID=ffd2fe61-9278-489e-9b96-3816394c9cb6&displayLang=en
If you didn’t have this tool you’d have to do this.
Download Exchange 2007 SP2
http://www.microsoft.com/downloads/details.aspx?FamilyID=4C4BD2A3-5E50-42B0-8BBB-2CC9AFE3216A&displaylang=en
How to install Exchange 2007 SP2 on SBS2008 without tool
http://support.microsoft.com/default.aspx?scid=kb;EN-US;973862
Labels: Exchange07, SBS2008
Sunday, December 27, 2009
PDF Handler for Vista not working in outlook 2007 on Win7 64bit
I found this fix from Leo Davidson,
for PDF Handler not working in Outlook 2007 on Win7 64bit and it Works Great!
Frome Source Page
http://www.pretentiousname.com/adobe_pdf_x64_fix/
Download Fix
http://www.pretentiousname.com/adobe_pdf_x64_fix/Reader_x64_fixer_1001_source.zip
Alternate Download: (Without permission from Leo)
http://www.sbits.biz/PDFviewerfix/Reader_x64_fixer_1001.zip
Thanks Leo :)
for PDF Handler not working in Outlook 2007 on Win7 64bit and it Works Great!
Frome Source Page
http://www.pretentiousname.com/adobe_pdf_x64_fix/
Download Fix
http://www.pretentiousname.com/adobe_pdf_x64_fix/Reader_x64_fixer_1001_source.zip
Alternate Download: (Without permission from Leo)
http://www.sbits.biz/PDFviewerfix/Reader_x64_fixer_1001.zip
Thanks Leo :)
Labels: 64bit, Outlook2007, Win7
Wednesday, December 16, 2009
Improve RWW Performance in SBS2008
SBS2008 RWW Has Changed the way RWW works
For one thing There is no Default Connect To Local Drives Option in RWW
Next it Automatically Enables the Background Image During a REMOTE RWW Session
(Which is Stupid IMO)
Below are some notes I've found across the web in speeding up RWW Experiance on SBS2008 *Use at your own perial
First thing I'd like to Address is NO Local Hard Drive Access Option in RWW
Let me guess You'd like to see this?

Where you Have the Option to Show Local drives and Ports.
To Enable this.
In Directory
C:\Program Files\Windows Small Business Server\Bin\webapp\Remote
Find tsweb.aspx
First thing make a backup Copy of this file
then open up Notepad in an elevated mode and then make the changes.
For Remote drives find!
MsRdpClient.AdvancedSettings2.RedirectDrives = FALSE
and set it to TRUE
If you want Remote Port Access Find
MsRdpClient.AdvancedSettings2.RedirectPorts = FALSE
And set it to TRUE
There are other things you can change but that will give you Remote Port and Drives.
Next is a way to Speed up RWW since RWW Defaults Allows the Background to display.
a. Again open notepad in elevated mode and open above file
b. Find the line "' Performance settings"
c. Insert this line below it
"MsRdpClient.AdvancedSettings2.PerformanceFlags = 111"
What this does: According to http://msdn.microsoft.com/en-us/library/aa381215(VS.85).aspx, you see it will disable Wallpaper, Full-window drag, Menu animations, Themes, Cursor shadow, Cursor blinking. So basically you can also change the value 111 to something else to just disable some of them.
2. Screen size:
Actually we have the logic to limit the TS window resolution to 1600*1200 as maximum. The reason is some low RDP version will not support the size larger than that. If you do want to use full screen size, and you don't have an low RDP version that will be using on a large resolution monitor (local one) (say using RDP 5.x or 6.0 on a 1920*1080 resolution monitor), then you could do below things to remove the limitation.
Steps:
a. Open notepad in elevated mode and open file (C:\Program Files\Windows Small Business Server\Bin\webapp\Remote\tsweb.aspx)
b. Find below content
if ( screen.width > 1600 ) then
sresWidth = 1600
else
sresWidth = screen.width
end if
if ( screen.height > 1200 ) then
sresHeight = 1200
else
sresHeight = screen.height
end if
c. replace them to
sresWidth = screen.width
sresHeight = screen.height
Note: after change this, if you do remote from RDP 5.x on a 1920*1080 resolution monitor, then most likely it will be failed with errors.
And the RDP 5.x are shipping with Windows XP SP2, RDP 6.0 are shipping with Vista RTM
The edited ASP Can be found here
http://www.sbits.biz/rwwfix/
(This only includes the Drive, ports and Background mods does not contain the screen resolution mod.) Use at own risk! :)
For one thing There is no Default Connect To Local Drives Option in RWW
Next it Automatically Enables the Background Image During a REMOTE RWW Session
(Which is Stupid IMO)
Below are some notes I've found across the web in speeding up RWW Experiance on SBS2008 *Use at your own perial
First thing I'd like to Address is NO Local Hard Drive Access Option in RWW
Let me guess You'd like to see this?
Where you Have the Option to Show Local drives and Ports.
To Enable this.
In Directory
C:\Program Files\Windows Small Business Server\Bin\webapp\Remote
Find tsweb.aspx
First thing make a backup Copy of this file
then open up Notepad in an elevated mode and then make the changes.
For Remote drives find!
MsRdpClient.AdvancedSettings2.RedirectDrives = FALSE
and set it to TRUE
If you want Remote Port Access Find
MsRdpClient.AdvancedSettings2.RedirectPorts = FALSE
And set it to TRUE
There are other things you can change but that will give you Remote Port and Drives.
Next is a way to Speed up RWW since RWW Defaults Allows the Background to display.
a. Again open notepad in elevated mode and open above file
b. Find the line "' Performance settings"
c. Insert this line below it
"MsRdpClient.AdvancedSettings2.PerformanceFlags = 111"
What this does: According to http://msdn.microsoft.com/en-us/library/aa381215(VS.85).aspx, you see it will disable Wallpaper, Full-window drag, Menu animations, Themes, Cursor shadow, Cursor blinking. So basically you can also change the value 111 to something else to just disable some of them.
2. Screen size:
Actually we have the logic to limit the TS window resolution to 1600*1200 as maximum. The reason is some low RDP version will not support the size larger than that. If you do want to use full screen size, and you don't have an low RDP version that will be using on a large resolution monitor (local one) (say using RDP 5.x or 6.0 on a 1920*1080 resolution monitor), then you could do below things to remove the limitation.
Steps:
a. Open notepad in elevated mode and open file (C:\Program Files\Windows Small Business Server\Bin\webapp\Remote\tsweb.aspx)
b. Find below content
if ( screen.width > 1600 ) then
sresWidth = 1600
else
sresWidth = screen.width
end if
if ( screen.height > 1200 ) then
sresHeight = 1200
else
sresHeight = screen.height
end if
c. replace them to
sresWidth = screen.width
sresHeight = screen.height
Note: after change this, if you do remote from RDP 5.x on a 1920*1080 resolution monitor, then most likely it will be failed with errors.
And the RDP 5.x are shipping with Windows XP SP2, RDP 6.0 are shipping with Vista RTM
The edited ASP Can be found here
http://www.sbits.biz/rwwfix/
(This only includes the Drive, ports and Background mods does not contain the screen resolution mod.) Use at own risk! :)
Monday, November 16, 2009
How to troubleshoot performance issues in Outlook 2007 Size Limits for OST PST and Outlook Slow issues
Coppied from
http://support.microsoft.com/kb/940226
Very Good Article:
The performance issues may be caused by one or more of the following:
Insufficient computer specifications
The latest service pack for Outlook 2007 not installed
Large Personal Folders files (.pst) or Offline Folder files (.ost)
Outlook .ost files or .pst files that are stored on a drive with insufficient write performance
Third-party add-ins
Gadgets that access Outlook data (This only applies to Windows Vista)
Microsoft Office Communicator integration
Antivirus software interaction
Windows Desktop Search indexing
Incomplete closure of .pst files or .ost files
POP3 accounts on Windows Vista clients
Many Really Simple Syndication (RSS) feeds
To-Do Bar and Online mode with Exchange server
Back to the top
Does the computer meet the system requirements for the 2007 Office suite that you are using?
Make sure that the computer meets the system requirements for the 2007 Microsoft Office suite that you are using. For more information about the system requirements for the 2007 Office system, visit the following Microsoft Web site:
http://office.microsoft.com/en-us/outlook/HA101668651033.aspx (http://office.microsoft.com/en-us/outlook/HA101668651033.aspx)
If the computer meets only the minimum system requirements, you will not experience optimal performance of the 2007 Office suite.
Back to the top
Are you running the latest version of Outlook 2007?
We recommend that you run Outlook 2007 Service Pack 1 (SP1) with the February 2009 cumulative update. Outlook 2007 SP1 includes the changes from the performance update and from the Business Contact Manager update that is mentioned in this topic.
If you are running the release version of Outlook 2007, we recommend that you install the Service Pack 1 (SP1) update and the Outlook 2007 February 2009 cumulative update that is mentioned in the following Microsoft Knowledge Base article, 961752:
961752 (http://support.microsoft.com/kb/961752/ ) Description of the Outlook 2007 hotfix package (Outlook.msp): February 24, 2009
For more information about the Outlook product team's work on the February 2009 cumulative update, click the following article number to view the article in the Microsoft Knowledge Base:
968009 (http://support.microsoft.com/kb/968009/ ) Outlook 2007 improvements in the February 2009 cumulative update
Back to the top
Do you have a large .pst file or a large .ost file?
If you have a large .pst file or a large .ost file, you may experience application pauses during typical operations in Outlook. These typical operations include reading e-mail messages, moving e-mail messages, and deleting e-mail messages.
When you use Outlook 2007 with the Performance Update, or you use Outlook 2007 SP1 versions before the February 2009 cumulative update, the following .ost size guidelines generally apply:
Up to 2 gigabytes (GB): This size should provide a good user experience on most hardware.
Between 2 GB and 4 GB: This size is typically hardware dependent. Therefore, if you have a fast hard disk and much RAM, your experience will be better. However, slower hard drives, such as drives that are typically found on portable computers or early generation solid state drives (SSDs), experience some application pauses when the drives respond.
More than 4 GB: This size is where short pauses begin to occur on most hardware.
Very large, such as 10 GB or larger: This size increases the frequency of the short pauses, especially while you are downloading new e-mail. You can use Send/Receive groups to manually sync your mail. This synchronization minimizes changes in the local data file during heavy e-mail usage. For more information about how to manage Outlook synchronization, visit the following Microsoft Web sites:
http://office.microsoft.com/en-us/outlook/HP052421871033.aspx (http://office.microsoft.com/en-us/outlook/HP052421871033.aspx)
http://office.microsoft.com/en-us/outlook/HP030829231033.aspx (http://office.microsoft.com/en-us/outlook/HP030829231033.aspx)
When you use Outlook 2007 SP1 with the February 2009 cumulative update or higher, the following .ost size guidelines generally apply:
Up to 5 gigabytes (GB): This size should provide a good user experience on most hardware.
Between 5 GB and 10 GB: This size is typically hardware dependent. Therefore, if you have a fast hard disk and much RAM, your experience will be better. However, slower hard drives, such as drives that are typically found on portable computers or early generation solid state drives (SSDs), experience some application pauses when the drives respond.
More than 10 GB: This size is where short pauses begin to occur on most hardware.
Very large, such as 25 GB or larger: This size increases the frequency of the short pauses, especially while you are downloading new e-mail. As described above, you can use Send/Receive groups to manually sync your mail.
The default maximum size for a Unicode .pst or .ost file is approximately 20 GB. The following KB article describes how to increase the maximum size of a .pst or .ost file:
832925 (http://support.microsoft.com/kb/832925/ ) How to configure the size limit for both (.pst) and (.ost) files in Outlook 2007 and in Outlook 2003
The following blog post describes how to reduce the size of your local data file by using synchronization filters:
http://msexchangeteam.com/archive/2007/12/17/447750.aspx (http://msexchangeteam.com/archive/2007/12/17/447750.aspx)
This is a stop-gap solution and is provided here for reference if you cannot reduce the size of your mailbox. For example, you may be unable to reduce the size of your mailbox if you have to maintain an archive of all e-mail messages, both sent and received, over a time span of several years.
Back to the top
Are you running a computer that has a first generation Solid State Drive (SSD) or a slow rotational Hard Disk Drive (HDD)?
If you are running Outlook 2007 on a computer that has a first generation solid state drive (SSD) or a slow rotational hard disk drive (HDD), you may experience frequent pauses when you perform typical operations in Outlook.
Storing and retrieving data in an Outlook data file involves a high number of small noncontiguous reads and writes. A good metric to use when gauging data file performance on specific hardware is the disk drive’s noncontiguous write performance. The Windows performance team has provided a tool named WinSAT (see below for download and execution instructions) that can be used to benchmark specific disk drives. As you can see in the table below, the estimated experience for Outlook 2007 SP1 with the February 2009 cumulative update is better.
The WinSAT tool is part of the Windows Vista Upgrade Advisor and is included in Windows Vista. For non-Windows Vista-based computers, you can download the Windows Vista Upgrade Advisor here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=42B5AC83-C24F-4863-A389-3FFC194924F8&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=42B5AC83-C24F-4863-A389-3FFC194924F8&displaylang=en)
The following table shows an estimated Outlook experience based on the score returned by the WinSAT tool.
Collapse this tableExpand this tableWinSAT score Drive characteristics SP1 before Feb update SP1 after Feb update and later versions
Less than 15 MB/s Generation 1 and Generation 2 SSDs (early 2008) Unusable Reasonable, responsive, limited hangs and pauses
Between 15 MB/s and 30 MB/s Most Generation 2 SSDs (after April 2008); many 5400 rpm laptop rotational drives Many hangs and pauses throughout the day Reasonable, responsive, limited hangs and pauses
Between 30 MB/s and 40 MB/s Some high-end Generation 2 SSDs (after September 2008); many 7200 rpm rotational drives Reasonable, responsive, limited hangs and pauses Quick, responsive, only occasional hangs
Greater than 40 MB/s Generation 3 SSDs, both MLC and SLC technology (November 2008); many 10000 rpm rotational drives Quick, responsive, only occasional hangs Quick, responsive, rarely hangs
NOTE: The following command-line was used to generate the results for the above table.
Winsat disk -drive c -ran -write -count 10
The results are found in the C:\Windows\Performance\Winsat\Winsat.log file.
Back to the top
Do you have many items in a single folder?
If you have a large number of items in any single folder, you may experience performance issues during certain operations in Outlook while using Cached Exchange mode or using a Personal Folders (.pst) file. . These performance issues are especially noticeable when you switch into and out of that folder.
When you use Outlook 2007 with the Performance Update, or you use Outlook 2007 SP1 versions before the February 2009 cumulative update, generally, when 10,000 or more items are in a single folder, these issues can occur.
When you use Outlook 2007 SP1 with the February 2009 cumulative update or higher and have more than 50,000 items in a single folder, views other than Arranged By: Date can be slower.
We recommend that you move several items in these larger folders to separate folders in the same store or to an archive store, and use Arrange By: Date when running Service Pack 1 (SP1) with the February 2009 cumulative update for folders that have a large number of items.
If you are not using Cached Exchange mode, please review one of the following resources. The resources document some performance issues on an Exchange server that has high item counts and restricted views. Additionally, the resources discuss how these performance issues might affect the overall client user experience.
For more information about understanding the performance impact of high item counts and restricted views, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc535025.aspx (http://technet.microsoft.com/en-us/library/cc535025.aspx)
For more information about mailbox size limits, visit the following Microsoft Exchange Team blog entry:
http://msexchangeteam.com/archive/2005/03/14/395229.aspx (http://msexchangeteam.com/archive/2005/03/14/395229.aspx)
Back to the top
Do you have any nonessential add-ins or out-of-date add-ins that are installed in Outlook?
If you have nonessential add-ins installed, you may want to remove them from Outlook. To view the add-ins that are installed, follow these steps:
In Outlook, click Trust Center on the Tools menu.
Click Add-ins to display a list of the COM add-ins that are installed.
By default, the following COM add-ins are included in the 2007 Office system:
Microsoft Access Outlook Add-in for Data Collection and Publishing
Microsoft Exchange Unified Messaging
Microsoft Office Groove Proxy for Outlook Add-in
Microsoft Office SharePoint Server Colleague Import Add-in
Microsoft Office Outlook Mobile Service
Microsoft VBA for Outlook Add-in
OneNote Notes about Outlook Items
Windows Search E-mail Indexer
Any other COM add-ins that are listed in the Trust Center were installed by other software.
Outlook can also use Microsoft Exchange Server client extensions that may cause performance issues. To see the list of currently installed Exchange Server client extensions, click Exchange Client Extensions in the Manage list in the Add-ins section, and then click Go. The Add-In Manager dialog box displays the list of currently installed Exchange Server client extensions.
By default, the following Exchange Server client extensions are included in the 2007 Office system:
Delegate Access
Deleted Item Recovery
Exchange Extensions commands
Exchange Extensions property pages
Any other extensions that are listed in the Add-In Manager dialog box were installed by other software.
To determine whether the performance problem is caused by add-ins, run Outlook in safe mode. To do this, press and hold CTRL when you start Outlook. When Outlook starts in safe mode, all COM add-ins and Exchange Server client extensions are disabled.
If the problem goes away when Outlook is running in safe mode, it is likely that one of the add-ins is causing the performance issue. To troubleshoot possible problems that are caused by COM add-ins or Exchange Server client extensions, disable any items that you do not use regularly. Then, restart Outlook. If that does not resolve the problem, disable the remaining add-ins one by one. If that does not resolve the problem, the issue may not be caused by an add-in.
To disable COM add-ins, follow these steps:
On the Tools menu, click Trust Center.
Click Add-ins, click COM Add-ins in the Manage list, and then click Go.
In the COM Add-Ins dialog box, click to clear the check boxes for any COM add-ins that you want to disable.
After you disable the add-ins, click OK, and then restart Outlook.
To disable Exchange Server client extensions, follow these steps:
On the Tools menu, click Trust Center.
Click Add-ins, click Exchange Client Extensions in the Manage list, and then click Go.
In the Add-In Manager dialog box, click to clear the check boxes for any extensions that you want to disable.
After you disable the extensions, click OK, and then restart Outlook.
Back to the top
Did you install any gadgets that integrate with Outlook?
On a Windows Vista-based computer, remove any gadgets that you downloaded to show your Outlook data. For example, this data may include the Outlook calendar, Outlook tasks, Outlook mail, and Outlook contacts. To remove gadgets on a Windows Vista-based computer, follow these steps:
Click StartCollapse this imageExpand this image, and then click Control Panel.
Click Control Panel Home.
Click Programs.
Click Windows Sidebar Properties.
In the Maintenance section, click View list of running gadgets.
Click any gadget that you want to disable, and then click Remove.
For more information about the Windows Sidebar, view the "How do I customize Windows Sidebar?" Help topic in Windows Vista.
Back to the top
Is Outlook integration with Communicator enabled?
By default, Outlook includes feature integration with Microsoft Office Communicator. The features that Outlook and Communicator share relate primarily to presence information such as whether someone is busy, away, or in a meeting. To disable feature integration, follow these steps:
In Outlook, click Options on the Tools menu.
Click the Other tab, click to clear the Display online status next to a person name check box under Person Names, and then click OK.
Restart Outlook.
Back to the top
Is antivirus software running?
If your antivirus software includes integration with Outlook, you may experience performance issues in Outlook. In this case, you can disable all Outlook integration within the antivirus software. Or, you can disable any antivirus software add-ins that are installed in Outlook.
You may have to contact the antivirus manufacturer to determine how to configure the antivirus software to exclude any integration with Outlook or to exclude scanning in Outlook.
Back to the top
Did you install Windows Desktop Search on a Windows XP-based computer or install Outlook on a Windows Vista-based computer?
Windows Desktop Search (WDS) will index all data in .ost files and in .pst files. However, the indexing of Outlook data occurs only when Outlook is running. Therefore, you may have to leave Outlook running overnight to determine whether the performance issues were related to the building of your search indexes.
Performance issues may increase when Outlook is running in online mode. Such performance issues occur because running Outlook in online mode increases the load on the Exchange Server. This performance issue is especially noticeable when Outlook is configured in a non-default state to index the items from the Exchange Server to the local client index, and more than one user indexes the Outlook data at the same time by using Windows Desktop Search.
To determine the indexing status for Outlook data, follow these steps:
In Outlook, point to Instant Search on the Tools menu, and then click Indexing Status.
In the Microsoft Office Outlook dialog box, view the number of items that remain to be indexed.
The built-in back-off mechanisms in the indexing component of Windows Desktop Search pause the indexing of Outlook data when the system is under heavy use. The easiest way to let the indexing finish is to leave Outlook running overnight.
Additionally, performance issues are reduced when you run Outlook in Cached Exchange Mode. In this mode, Windows Desktop Search searches the local copy of the mailbox instead of the mailbox content that is located on the server.
Back to the top
Did the .pst file or the .ost file shut down incorrectly?
If you are running Service Pack 1 (SP1) with the February 2009 cumulative update, the frequency of the operations described in this section will be dramatically reduced.
If the .pst file or the .ost file shuts down incorrectly, you may receive one of the following error messages the next time that you start Outlook:
Error message 1
Outlook cannot open the data file filename until it has been checked for problems.
Error message 2
Microsoft Office Outlook’ exited without properly closing your Outlook data file ‘drive:\Users\username\AppData\Local\Microsoft\Outlook\outlook.ost’. ‘Microsoft Office Outlook’ must be restarted. If this error message recurs, contact support for ‘Microsoft Office Outlook’ for assistance.
Error message 3
The data file filename was not closed properly’. This file is being checked for problems.
If you receive one or more of these error messages, you may experience performance issues until Outlook finishes the reconciliation process for the .ost file or for the .pst file. The following gear icon is displayed in the status bar while Outlook checks the data file in the background:
Collapse this imageExpand this image
When this icon disappears, the .pst file or the .ost file is reconciled. If you are running Outlook 2007 SP1 without the February 2009 cumulative update, and you exit Outlook while the gear icon is present, reconciliation must restart the next time that you run Outlook. In this case, we recommend that you leave Outlook running until the gear icon disappears before you exit Outlook. If you are running Outlook 2007 SP1 with the February 2009 cumulative update, the reconciliation process will pause at shutdown and resume (from where it was paused) the next time you start Outlook.
An incorrectly shut down .ost file or .pst file may occur for one of the following reasons:
Antivirus scanning of the file
Forced Microsoft Windows shutdown before the Outlook.exe process shuts down completely
Outlook add-ins
If you see this issue frequently, and you have to exit Outlook shortly before you shut down your computer, it may be better to shut down Windows while Outlook is still running. We recommend that you do this instead of exiting Outlook and then shutting down Windows shortly after that.
Back to the top
Do you use a rule that moves items out of the default store?
Rules that move items from your default store into another store can cause performance issues when Outlook downloads e-mail messages. Such performance issues are especially prevalent if you are not running Outlook with the SP1 update.
If you are using rules to move mail from a POP3 account to another store, you can use new functionality in Outlook 2007 that lets you change the delivery location of the POP3 account. In this case, you do not have to use rules to deliver the mail from that account to the separate store.
To do this, follow these steps:
On the Tools menu, click Accounts, and then select the POP3 account in the list.
Click Change Folder at the bottom of the dialog box to select a folder in the separate store to which you want to deliver that account.
If you do not use a POP3 account, you can also work around this issue by setting your target folder for all rules to be in the same Outlook store. Then, use the AutoArchive feature to move messages out of the default store in bulk. For more information about how to configure the AutoArchive feature, click the following article number to view the article in the Microsoft Knowledge Base:
830119 (http://support.microsoft.com/kb/830119/ ) Description of the AutoArchive feature in Outlook 2007 and in Outlook 2003
Back to the top
Are you connected to a POP3 server?
For more information about a possible workaround if you are connected to a POP3 server and your download speeds are very slow, click the following article number to view the article in the Microsoft Knowledge Base:
935400 (http://support.microsoft.com/kb/935400/ ) It takes a very long time to download an e-mail message from a POP3 server in Outlook 2007
Back to the top
Are you synchronizing many RSS feeds?
If you are running Service Pack 1 (SP1) with the February 2009 cumulative update, the issues described in this section are significantly reduced in frequency.
If you are synchronizing many RSS feeds into Outlook, you may experience performance issues with certain ordinary operations. By default, all RSS feeds are synchronized automatically at set intervals. If you have too many feeds, Outlook may become unresponsive.
You can create a separate Send/Receive group that contains only your RSS feeds, and you can remove them from the group your default mail account is in. This will enable you to sync the RSS feeds on-demand instead of at set intervals.
For more information about how to manage Send/Receive groups, see the articles on the following Office Online Web site:
http://office.microsoft.com/en-us/outlook/CH101395511033.aspx (http://office.microsoft.com/en-us/outlook/CH101395511033.aspx)
Thank you! Your feedback is used to help us improve our support content. For more assistance options, visit the Help and Support Page (http://support.microsoft.com/) .
Back to the top
Are you running Outlook with the To-Do Bar enabled when Outlook is running in online mode against an Exchange server?
If you are running Outlook with the To-Do Bar enabled when Outlook is running in online mode against an Exchange server, the additional data that is displayed in the To-Do Bar is retrieved from the server. Therefore, additional data requests are performed. These additional data requests for the To-Do Bar cause additional network traffic that can affect the performance of some standard Outlook operations.
If you are running Service Pack 1 (SP1) with the February 2009 cumulative update, the amount of network traffic caused by the To-Do Bar has been reduced from earlier versions, especially when loading recurring calendar items.
To avoid additional network traffic and the resulting performance effect in Outlook, you can turn off the To-Do Bar and reduce the network traffic between Outlook and Exchange in online mode. This reduction in data retrieval requests affects the user experience most significantly if you have a network that has high latency or limited bandwidth. To turn off the To-Do Bar in Outlook, point to To-Do Bar on the View menu, and then click Off.
Administrators can also disable the To-Do Bar on users’ computers by using the following registry information.
If you do not use a policy setting, use the following information.
Registry location: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\ToDoBar
Value name: DisableToDoBar
Value type: DWORD
Value data: 1 or 0
Note If the value data is set to 1, the To-Do Bar is turned off. If the value data is set to 0, the To-Do Bar is turned on.
If you use a policy setting, use the following information.
Registry location: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\Options\ToDoBar
Value name: DisableToDoBar
Value type: DWORD
Value data: 1 or 0
Note If the value data is set to 1, the To-Do Bar is turned off. If the value data is set to 0, the To-Do Bar is turned on.
For more information about how administrators can control the user interface through policy settings, visit the following Microsoft Web sites:
http://technet.microsoft.com/en-us/library/cc178990.aspx (http://technet.microsoft.com/en-us/library/cc178990.aspx)
http://technet.microsoft.com/en-us/library/cc179100.aspx (http://technet.microsoft.com/en-us/library/cc179100.aspx)
http://support.microsoft.com/kb/940226
Very Good Article:
The performance issues may be caused by one or more of the following:
Insufficient computer specifications
The latest service pack for Outlook 2007 not installed
Large Personal Folders files (.pst) or Offline Folder files (.ost)
Outlook .ost files or .pst files that are stored on a drive with insufficient write performance
Third-party add-ins
Gadgets that access Outlook data (This only applies to Windows Vista)
Microsoft Office Communicator integration
Antivirus software interaction
Windows Desktop Search indexing
Incomplete closure of .pst files or .ost files
POP3 accounts on Windows Vista clients
Many Really Simple Syndication (RSS) feeds
To-Do Bar and Online mode with Exchange server
Back to the top
Does the computer meet the system requirements for the 2007 Office suite that you are using?
Make sure that the computer meets the system requirements for the 2007 Microsoft Office suite that you are using. For more information about the system requirements for the 2007 Office system, visit the following Microsoft Web site:
http://office.microsoft.com/en-us/outlook/HA101668651033.aspx (http://office.microsoft.com/en-us/outlook/HA101668651033.aspx)
If the computer meets only the minimum system requirements, you will not experience optimal performance of the 2007 Office suite.
Back to the top
Are you running the latest version of Outlook 2007?
We recommend that you run Outlook 2007 Service Pack 1 (SP1) with the February 2009 cumulative update. Outlook 2007 SP1 includes the changes from the performance update and from the Business Contact Manager update that is mentioned in this topic.
If you are running the release version of Outlook 2007, we recommend that you install the Service Pack 1 (SP1) update and the Outlook 2007 February 2009 cumulative update that is mentioned in the following Microsoft Knowledge Base article, 961752:
961752 (http://support.microsoft.com/kb/961752/ ) Description of the Outlook 2007 hotfix package (Outlook.msp): February 24, 2009
For more information about the Outlook product team's work on the February 2009 cumulative update, click the following article number to view the article in the Microsoft Knowledge Base:
968009 (http://support.microsoft.com/kb/968009/ ) Outlook 2007 improvements in the February 2009 cumulative update
Back to the top
Do you have a large .pst file or a large .ost file?
If you have a large .pst file or a large .ost file, you may experience application pauses during typical operations in Outlook. These typical operations include reading e-mail messages, moving e-mail messages, and deleting e-mail messages.
When you use Outlook 2007 with the Performance Update, or you use Outlook 2007 SP1 versions before the February 2009 cumulative update, the following .ost size guidelines generally apply:
Up to 2 gigabytes (GB): This size should provide a good user experience on most hardware.
Between 2 GB and 4 GB: This size is typically hardware dependent. Therefore, if you have a fast hard disk and much RAM, your experience will be better. However, slower hard drives, such as drives that are typically found on portable computers or early generation solid state drives (SSDs), experience some application pauses when the drives respond.
More than 4 GB: This size is where short pauses begin to occur on most hardware.
Very large, such as 10 GB or larger: This size increases the frequency of the short pauses, especially while you are downloading new e-mail. You can use Send/Receive groups to manually sync your mail. This synchronization minimizes changes in the local data file during heavy e-mail usage. For more information about how to manage Outlook synchronization, visit the following Microsoft Web sites:
http://office.microsoft.com/en-us/outlook/HP052421871033.aspx (http://office.microsoft.com/en-us/outlook/HP052421871033.aspx)
http://office.microsoft.com/en-us/outlook/HP030829231033.aspx (http://office.microsoft.com/en-us/outlook/HP030829231033.aspx)
When you use Outlook 2007 SP1 with the February 2009 cumulative update or higher, the following .ost size guidelines generally apply:
Up to 5 gigabytes (GB): This size should provide a good user experience on most hardware.
Between 5 GB and 10 GB: This size is typically hardware dependent. Therefore, if you have a fast hard disk and much RAM, your experience will be better. However, slower hard drives, such as drives that are typically found on portable computers or early generation solid state drives (SSDs), experience some application pauses when the drives respond.
More than 10 GB: This size is where short pauses begin to occur on most hardware.
Very large, such as 25 GB or larger: This size increases the frequency of the short pauses, especially while you are downloading new e-mail. As described above, you can use Send/Receive groups to manually sync your mail.
The default maximum size for a Unicode .pst or .ost file is approximately 20 GB. The following KB article describes how to increase the maximum size of a .pst or .ost file:
832925 (http://support.microsoft.com/kb/832925/ ) How to configure the size limit for both (.pst) and (.ost) files in Outlook 2007 and in Outlook 2003
The following blog post describes how to reduce the size of your local data file by using synchronization filters:
http://msexchangeteam.com/archive/2007/12/17/447750.aspx (http://msexchangeteam.com/archive/2007/12/17/447750.aspx)
This is a stop-gap solution and is provided here for reference if you cannot reduce the size of your mailbox. For example, you may be unable to reduce the size of your mailbox if you have to maintain an archive of all e-mail messages, both sent and received, over a time span of several years.
Back to the top
Are you running a computer that has a first generation Solid State Drive (SSD) or a slow rotational Hard Disk Drive (HDD)?
If you are running Outlook 2007 on a computer that has a first generation solid state drive (SSD) or a slow rotational hard disk drive (HDD), you may experience frequent pauses when you perform typical operations in Outlook.
Storing and retrieving data in an Outlook data file involves a high number of small noncontiguous reads and writes. A good metric to use when gauging data file performance on specific hardware is the disk drive’s noncontiguous write performance. The Windows performance team has provided a tool named WinSAT (see below for download and execution instructions) that can be used to benchmark specific disk drives. As you can see in the table below, the estimated experience for Outlook 2007 SP1 with the February 2009 cumulative update is better.
The WinSAT tool is part of the Windows Vista Upgrade Advisor and is included in Windows Vista. For non-Windows Vista-based computers, you can download the Windows Vista Upgrade Advisor here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=42B5AC83-C24F-4863-A389-3FFC194924F8&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=42B5AC83-C24F-4863-A389-3FFC194924F8&displaylang=en)
The following table shows an estimated Outlook experience based on the score returned by the WinSAT tool.
Collapse this tableExpand this tableWinSAT score Drive characteristics SP1 before Feb update SP1 after Feb update and later versions
Less than 15 MB/s Generation 1 and Generation 2 SSDs (early 2008) Unusable Reasonable, responsive, limited hangs and pauses
Between 15 MB/s and 30 MB/s Most Generation 2 SSDs (after April 2008); many 5400 rpm laptop rotational drives Many hangs and pauses throughout the day Reasonable, responsive, limited hangs and pauses
Between 30 MB/s and 40 MB/s Some high-end Generation 2 SSDs (after September 2008); many 7200 rpm rotational drives Reasonable, responsive, limited hangs and pauses Quick, responsive, only occasional hangs
Greater than 40 MB/s Generation 3 SSDs, both MLC and SLC technology (November 2008); many 10000 rpm rotational drives Quick, responsive, only occasional hangs Quick, responsive, rarely hangs
NOTE: The following command-line was used to generate the results for the above table.
Winsat disk -drive c -ran -write -count 10
The results are found in the C:\Windows\Performance\Winsat\Winsat.log file.
Back to the top
Do you have many items in a single folder?
If you have a large number of items in any single folder, you may experience performance issues during certain operations in Outlook while using Cached Exchange mode or using a Personal Folders (.pst) file. . These performance issues are especially noticeable when you switch into and out of that folder.
When you use Outlook 2007 with the Performance Update, or you use Outlook 2007 SP1 versions before the February 2009 cumulative update, generally, when 10,000 or more items are in a single folder, these issues can occur.
When you use Outlook 2007 SP1 with the February 2009 cumulative update or higher and have more than 50,000 items in a single folder, views other than Arranged By: Date can be slower.
We recommend that you move several items in these larger folders to separate folders in the same store or to an archive store, and use Arrange By: Date when running Service Pack 1 (SP1) with the February 2009 cumulative update for folders that have a large number of items.
If you are not using Cached Exchange mode, please review one of the following resources. The resources document some performance issues on an Exchange server that has high item counts and restricted views. Additionally, the resources discuss how these performance issues might affect the overall client user experience.
For more information about understanding the performance impact of high item counts and restricted views, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc535025.aspx (http://technet.microsoft.com/en-us/library/cc535025.aspx)
For more information about mailbox size limits, visit the following Microsoft Exchange Team blog entry:
http://msexchangeteam.com/archive/2005/03/14/395229.aspx (http://msexchangeteam.com/archive/2005/03/14/395229.aspx)
Back to the top
Do you have any nonessential add-ins or out-of-date add-ins that are installed in Outlook?
If you have nonessential add-ins installed, you may want to remove them from Outlook. To view the add-ins that are installed, follow these steps:
In Outlook, click Trust Center on the Tools menu.
Click Add-ins to display a list of the COM add-ins that are installed.
By default, the following COM add-ins are included in the 2007 Office system:
Microsoft Access Outlook Add-in for Data Collection and Publishing
Microsoft Exchange Unified Messaging
Microsoft Office Groove Proxy for Outlook Add-in
Microsoft Office SharePoint Server Colleague Import Add-in
Microsoft Office Outlook Mobile Service
Microsoft VBA for Outlook Add-in
OneNote Notes about Outlook Items
Windows Search E-mail Indexer
Any other COM add-ins that are listed in the Trust Center were installed by other software.
Outlook can also use Microsoft Exchange Server client extensions that may cause performance issues. To see the list of currently installed Exchange Server client extensions, click Exchange Client Extensions in the Manage list in the Add-ins section, and then click Go. The Add-In Manager dialog box displays the list of currently installed Exchange Server client extensions.
By default, the following Exchange Server client extensions are included in the 2007 Office system:
Delegate Access
Deleted Item Recovery
Exchange Extensions commands
Exchange Extensions property pages
Any other extensions that are listed in the Add-In Manager dialog box were installed by other software.
To determine whether the performance problem is caused by add-ins, run Outlook in safe mode. To do this, press and hold CTRL when you start Outlook. When Outlook starts in safe mode, all COM add-ins and Exchange Server client extensions are disabled.
If the problem goes away when Outlook is running in safe mode, it is likely that one of the add-ins is causing the performance issue. To troubleshoot possible problems that are caused by COM add-ins or Exchange Server client extensions, disable any items that you do not use regularly. Then, restart Outlook. If that does not resolve the problem, disable the remaining add-ins one by one. If that does not resolve the problem, the issue may not be caused by an add-in.
To disable COM add-ins, follow these steps:
On the Tools menu, click Trust Center.
Click Add-ins, click COM Add-ins in the Manage list, and then click Go.
In the COM Add-Ins dialog box, click to clear the check boxes for any COM add-ins that you want to disable.
After you disable the add-ins, click OK, and then restart Outlook.
To disable Exchange Server client extensions, follow these steps:
On the Tools menu, click Trust Center.
Click Add-ins, click Exchange Client Extensions in the Manage list, and then click Go.
In the Add-In Manager dialog box, click to clear the check boxes for any extensions that you want to disable.
After you disable the extensions, click OK, and then restart Outlook.
Back to the top
Did you install any gadgets that integrate with Outlook?
On a Windows Vista-based computer, remove any gadgets that you downloaded to show your Outlook data. For example, this data may include the Outlook calendar, Outlook tasks, Outlook mail, and Outlook contacts. To remove gadgets on a Windows Vista-based computer, follow these steps:
Click StartCollapse this imageExpand this image, and then click Control Panel.
Click Control Panel Home.
Click Programs.
Click Windows Sidebar Properties.
In the Maintenance section, click View list of running gadgets.
Click any gadget that you want to disable, and then click Remove.
For more information about the Windows Sidebar, view the "How do I customize Windows Sidebar?" Help topic in Windows Vista.
Back to the top
Is Outlook integration with Communicator enabled?
By default, Outlook includes feature integration with Microsoft Office Communicator. The features that Outlook and Communicator share relate primarily to presence information such as whether someone is busy, away, or in a meeting. To disable feature integration, follow these steps:
In Outlook, click Options on the Tools menu.
Click the Other tab, click to clear the Display online status next to a person name check box under Person Names, and then click OK.
Restart Outlook.
Back to the top
Is antivirus software running?
If your antivirus software includes integration with Outlook, you may experience performance issues in Outlook. In this case, you can disable all Outlook integration within the antivirus software. Or, you can disable any antivirus software add-ins that are installed in Outlook.
You may have to contact the antivirus manufacturer to determine how to configure the antivirus software to exclude any integration with Outlook or to exclude scanning in Outlook.
Back to the top
Did you install Windows Desktop Search on a Windows XP-based computer or install Outlook on a Windows Vista-based computer?
Windows Desktop Search (WDS) will index all data in .ost files and in .pst files. However, the indexing of Outlook data occurs only when Outlook is running. Therefore, you may have to leave Outlook running overnight to determine whether the performance issues were related to the building of your search indexes.
Performance issues may increase when Outlook is running in online mode. Such performance issues occur because running Outlook in online mode increases the load on the Exchange Server. This performance issue is especially noticeable when Outlook is configured in a non-default state to index the items from the Exchange Server to the local client index, and more than one user indexes the Outlook data at the same time by using Windows Desktop Search.
To determine the indexing status for Outlook data, follow these steps:
In Outlook, point to Instant Search on the Tools menu, and then click Indexing Status.
In the Microsoft Office Outlook dialog box, view the number of items that remain to be indexed.
The built-in back-off mechanisms in the indexing component of Windows Desktop Search pause the indexing of Outlook data when the system is under heavy use. The easiest way to let the indexing finish is to leave Outlook running overnight.
Additionally, performance issues are reduced when you run Outlook in Cached Exchange Mode. In this mode, Windows Desktop Search searches the local copy of the mailbox instead of the mailbox content that is located on the server.
Back to the top
Did the .pst file or the .ost file shut down incorrectly?
If you are running Service Pack 1 (SP1) with the February 2009 cumulative update, the frequency of the operations described in this section will be dramatically reduced.
If the .pst file or the .ost file shuts down incorrectly, you may receive one of the following error messages the next time that you start Outlook:
Error message 1
Outlook cannot open the data file filename until it has been checked for problems.
Error message 2
Microsoft Office Outlook’ exited without properly closing your Outlook data file ‘drive:\Users\username\AppData\Local\Microsoft\Outlook\outlook.ost’. ‘Microsoft Office Outlook’ must be restarted. If this error message recurs, contact support for ‘Microsoft Office Outlook’ for assistance.
Error message 3
The data file filename was not closed properly’. This file is being checked for problems.
If you receive one or more of these error messages, you may experience performance issues until Outlook finishes the reconciliation process for the .ost file or for the .pst file. The following gear icon is displayed in the status bar while Outlook checks the data file in the background:
Collapse this imageExpand this image
When this icon disappears, the .pst file or the .ost file is reconciled. If you are running Outlook 2007 SP1 without the February 2009 cumulative update, and you exit Outlook while the gear icon is present, reconciliation must restart the next time that you run Outlook. In this case, we recommend that you leave Outlook running until the gear icon disappears before you exit Outlook. If you are running Outlook 2007 SP1 with the February 2009 cumulative update, the reconciliation process will pause at shutdown and resume (from where it was paused) the next time you start Outlook.
An incorrectly shut down .ost file or .pst file may occur for one of the following reasons:
Antivirus scanning of the file
Forced Microsoft Windows shutdown before the Outlook.exe process shuts down completely
Outlook add-ins
If you see this issue frequently, and you have to exit Outlook shortly before you shut down your computer, it may be better to shut down Windows while Outlook is still running. We recommend that you do this instead of exiting Outlook and then shutting down Windows shortly after that.
Back to the top
Do you use a rule that moves items out of the default store?
Rules that move items from your default store into another store can cause performance issues when Outlook downloads e-mail messages. Such performance issues are especially prevalent if you are not running Outlook with the SP1 update.
If you are using rules to move mail from a POP3 account to another store, you can use new functionality in Outlook 2007 that lets you change the delivery location of the POP3 account. In this case, you do not have to use rules to deliver the mail from that account to the separate store.
To do this, follow these steps:
On the Tools menu, click Accounts, and then select the POP3 account in the list.
Click Change Folder at the bottom of the dialog box to select a folder in the separate store to which you want to deliver that account.
If you do not use a POP3 account, you can also work around this issue by setting your target folder for all rules to be in the same Outlook store. Then, use the AutoArchive feature to move messages out of the default store in bulk. For more information about how to configure the AutoArchive feature, click the following article number to view the article in the Microsoft Knowledge Base:
830119 (http://support.microsoft.com/kb/830119/ ) Description of the AutoArchive feature in Outlook 2007 and in Outlook 2003
Back to the top
Are you connected to a POP3 server?
For more information about a possible workaround if you are connected to a POP3 server and your download speeds are very slow, click the following article number to view the article in the Microsoft Knowledge Base:
935400 (http://support.microsoft.com/kb/935400/ ) It takes a very long time to download an e-mail message from a POP3 server in Outlook 2007
Back to the top
Are you synchronizing many RSS feeds?
If you are running Service Pack 1 (SP1) with the February 2009 cumulative update, the issues described in this section are significantly reduced in frequency.
If you are synchronizing many RSS feeds into Outlook, you may experience performance issues with certain ordinary operations. By default, all RSS feeds are synchronized automatically at set intervals. If you have too many feeds, Outlook may become unresponsive.
You can create a separate Send/Receive group that contains only your RSS feeds, and you can remove them from the group your default mail account is in. This will enable you to sync the RSS feeds on-demand instead of at set intervals.
For more information about how to manage Send/Receive groups, see the articles on the following Office Online Web site:
http://office.microsoft.com/en-us/outlook/CH101395511033.aspx (http://office.microsoft.com/en-us/outlook/CH101395511033.aspx)
Thank you! Your feedback is used to help us improve our support content. For more assistance options, visit the Help and Support Page (http://support.microsoft.com/) .
Back to the top
Are you running Outlook with the To-Do Bar enabled when Outlook is running in online mode against an Exchange server?
If you are running Outlook with the To-Do Bar enabled when Outlook is running in online mode against an Exchange server, the additional data that is displayed in the To-Do Bar is retrieved from the server. Therefore, additional data requests are performed. These additional data requests for the To-Do Bar cause additional network traffic that can affect the performance of some standard Outlook operations.
If you are running Service Pack 1 (SP1) with the February 2009 cumulative update, the amount of network traffic caused by the To-Do Bar has been reduced from earlier versions, especially when loading recurring calendar items.
To avoid additional network traffic and the resulting performance effect in Outlook, you can turn off the To-Do Bar and reduce the network traffic between Outlook and Exchange in online mode. This reduction in data retrieval requests affects the user experience most significantly if you have a network that has high latency or limited bandwidth. To turn off the To-Do Bar in Outlook, point to To-Do Bar on the View menu, and then click Off.
Administrators can also disable the To-Do Bar on users’ computers by using the following registry information.
If you do not use a policy setting, use the following information.
Registry location: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\ToDoBar
Value name: DisableToDoBar
Value type: DWORD
Value data: 1 or 0
Note If the value data is set to 1, the To-Do Bar is turned off. If the value data is set to 0, the To-Do Bar is turned on.
If you use a policy setting, use the following information.
Registry location: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\Options\ToDoBar
Value name: DisableToDoBar
Value type: DWORD
Value data: 1 or 0
Note If the value data is set to 1, the To-Do Bar is turned off. If the value data is set to 0, the To-Do Bar is turned on.
For more information about how administrators can control the user interface through policy settings, visit the following Microsoft Web sites:
http://technet.microsoft.com/en-us/library/cc178990.aspx (http://technet.microsoft.com/en-us/library/cc178990.aspx)
http://technet.microsoft.com/en-us/library/cc179100.aspx (http://technet.microsoft.com/en-us/library/cc179100.aspx)
Labels: Exchange03, Exchange07, Outlook2003, Outlook2007
Sunday, November 08, 2009
0X80004005 Error
From http://support.microsoft.com/kb/318908
If you are using a Microsoft Outlook client computer, you cannot download an offline Address Book. When you try to download an Address Book in Outlook, the following error is logged in the synchronization log:
7:59:00 Microsoft Exchange offline address book
7:59:00 0X80004005
This issue may occur if the mailbox store has not been associated with a valid o...This issue may occur if the mailbox store has not been associated with a valid offline Address Book.
Back to the top
To resolve this issue, follow these steps: Start Exchange System Manager. Expand...To resolve this issue, follow these steps:
Start Exchange System Manager.
Expand Organization, and then expand Administrative Groups.
If "Administrative Groups" does not appear under Organization, make sure that you have configured Exchange System Manager to display Administrative Groups. To do so, right-click Organization, click Properties, and then click Display administrative groups.
Expand the administrative group to which the server belongs.
Expand Servers, expand the server that you want to configure, and then expand First Storage Group.
Right-click Mailbox Store, and then click Properties.
In the Offline Address Book section, make sure that a valid offline Address Book is listed.
If one is not listed, click Browse, and then click a valid offline Address Book. You can use Default Offline Address Book as the default setting.
If you are using a Microsoft Outlook client computer, you cannot download an offline Address Book. When you try to download an Address Book in Outlook, the following error is logged in the synchronization log:
7:59:00 Microsoft Exchange offline address book
7:59:00 0X80004005
This issue may occur if the mailbox store has not been associated with a valid o...This issue may occur if the mailbox store has not been associated with a valid offline Address Book.
Back to the top
To resolve this issue, follow these steps: Start Exchange System Manager. Expand...To resolve this issue, follow these steps:
Start Exchange System Manager.
Expand Organization, and then expand Administrative Groups.
If "Administrative Groups" does not appear under Organization, make sure that you have configured Exchange System Manager to display Administrative Groups. To do so, right-click Organization, click Properties, and then click Display administrative groups.
Expand the administrative group to which the server belongs.
Expand Servers, expand the server that you want to configure, and then expand First Storage Group.
Right-click Mailbox Store, and then click Properties.
In the Offline Address Book section, make sure that a valid offline Address Book is listed.
If one is not listed, click Browse, and then click a valid offline Address Book. You can use Default Offline Address Book as the default setting.
Labels: Exchange03
Thursday, October 22, 2009
How to test a Fax. (Free Fax Test)
HP Fax Test Instructions
To test the capability of your fax machine, follow the directions below.
NOTE: Be sure that your phone number is not Caller ID blocked by your telephone company prior to attempting to send and receive a fax. Pressing *82 before dialing the toll free number will unblock the Caller ID blocking feature in most areas. Other phone company services can prevent you from receiving a fax, including voice mail, call blocking, or call privacy features.
NOTE: Whenever troubleshooting a fax issue, it is good practice to set the Automatic Reports option to Every Error before attempting a test fax. This way, even if the sent fax fails, an error code will be generated that will guide you in future troubleshooting. This option is available in different places on different products, consult the product User's Guide for specific steps.
Send a one page black and white text fax to
1-888-hpfaxme (1-888-473-2963).
When your fax is received by the HP Test Fax Service, we will generate a return fax to you within five minutes confirming that we received your fax. This verifies that you can both send and receive a fax with your fax machine.
If you do not receive a return fax within 5-7 minutes, there may be a problem with the setup of your fax machine. Consult the user manual that came with the product for proper setup and configuration.
NOTE: The most common cause of failure is that the fax number set in the Fax Header on the machine does not match the number of the phone line connected to the fax. Also, ensure that the fax header contains the full 10-digit telephone number of the fax machine, including the area code.
To test the capability of your fax machine, follow the directions below.
NOTE: Be sure that your phone number is not Caller ID blocked by your telephone company prior to attempting to send and receive a fax. Pressing *82 before dialing the toll free number will unblock the Caller ID blocking feature in most areas. Other phone company services can prevent you from receiving a fax, including voice mail, call blocking, or call privacy features.
NOTE: Whenever troubleshooting a fax issue, it is good practice to set the Automatic Reports option to Every Error before attempting a test fax. This way, even if the sent fax fails, an error code will be generated that will guide you in future troubleshooting. This option is available in different places on different products, consult the product User's Guide for specific steps.
Send a one page black and white text fax to
1-888-hpfaxme (1-888-473-2963).
When your fax is received by the HP Test Fax Service, we will generate a return fax to you within five minutes confirming that we received your fax. This verifies that you can both send and receive a fax with your fax machine.
If you do not receive a return fax within 5-7 minutes, there may be a problem with the setup of your fax machine. Consult the user manual that came with the product for proper setup and configuration.
NOTE: The most common cause of failure is that the fax number set in the Fax Header on the machine does not match the number of the phone line connected to the fax. Also, ensure that the fax header contains the full 10-digit telephone number of the fax machine, including the area code.
Thursday, September 10, 2009
Why small businesses use Windows Small Business Server
Why small businesses use Windows Small Business Server:
http://blogs.technet.com/sbs/archive/2009/09/10/why-small-businesses-use-windows-small-business-server.aspx
http://blogs.technet.com/sbs/archive/2009/09/10/why-small-businesses-use-windows-small-business-server.aspx
Friday, August 28, 2009
SBS2008 not sending email out on a Dell PE2900
Issue with SBS2008 Sending email out on a Dell PE2900
Mail would receive just fine into the SBS2008 however sending email out would get stuck halfway and never get delivered.
No Return Bounce NO indication of any issues.
Found out that Broadcom NIC was the issue in the Dell PE2900
Even though it had Version 9 drivers Dell claimed that version 12 “Might”
I repeat “MIGHT” work.
Instead of dealing with it not working after new drivers, I disabled Onboard NICs
Purchased a DLINK 1GB Nic Card.
Installed and mail going out correctly now with no issues!
Information Courtesy of Lafayette Jefferson.
Mail would receive just fine into the SBS2008 however sending email out would get stuck halfway and never get delivered.
No Return Bounce NO indication of any issues.
Found out that Broadcom NIC was the issue in the Dell PE2900
Even though it had Version 9 drivers Dell claimed that version 12 “Might”
I repeat “MIGHT” work.
Instead of dealing with it not working after new drivers, I disabled Onboard NICs
Purchased a DLINK 1GB Nic Card.
Installed and mail going out correctly now with no issues!
Information Courtesy of Lafayette Jefferson.
Labels: Dell, Exchange07, SBS2008
Sunday, August 23, 2009
How to get WINS to work with SBS2008 over VPN
Info Taken From:
http://nicholas.piasecki.name/blog/2009/06/getting-wins-like-computer-name-resolution-over-vpn-in-sbs-2008/
By Nicholas Piasecki:
So this week concluded several sleepless nights and much heartburn as I migrated Skiviez’s SBS 2003 machine (running as our domain controller and our mail server) to SBS 2008. As far as things go, it went relatively smoothly, and the remainder of the week was dealing with lots of small niceties that I had forgotten that I had set up on the 2003 server that I now needed to set up once again.
One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as \\COMPUTER-NAME\SHARE-NAME; for example, \\CYRUS\Pickup Holding, because for some reason some of the older servers are named after my boss’s dead cats.
When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when \\CYRUS\Pickup Holding failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding would work fine. This was super annoying.
The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008 finally retires this ancient technology by default, however, so I had two choices: I could either install the WINS server role on SBS 2008, or I could just figure out how to get the 015 DNS Domain Name option from DHCP to relay through the VPN connection.
I chose the latter option, since it’s certainly less confusing to be able to say to someone in the future “we don’t use WINS, DNS does everything.” So here’s how to do it:
1.On the SBS 2008 server, click Start > Administrative Tools > Routing and Remote Access.
2.In the tree view, drill down past the server name to IPV4 > General. Right-click the General option and choose “New Routing Protocol” and choose DHCP Relay Agent.
3.Now right-click the newly appended “DHCP Relay Agent” node and choose Properties. Add the IP address of your DHCP server (which is probably your SBS server itself), and click OK. Then click it again and choose “New Interface” and add the “Internal” interface.
4.Now if you connect through VPN, an ipconfig /all should show your domain name as a “Connection-specific DNS suffix” and pinging machines by their suffix-less computer names should work. (If it doesn’t, make sure your DHCP server is using that 015 DNS Domain Name option, which the SBS 2008 wizards set up by default.)
http://nicholas.piasecki.name/blog/2009/06/getting-wins-like-computer-name-resolution-over-vpn-in-sbs-2008/
By Nicholas Piasecki:
So this week concluded several sleepless nights and much heartburn as I migrated Skiviez’s SBS 2003 machine (running as our domain controller and our mail server) to SBS 2008. As far as things go, it went relatively smoothly, and the remainder of the week was dealing with lots of small niceties that I had forgotten that I had set up on the 2003 server that I now needed to set up once again.
One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as \\COMPUTER-NAME\SHARE-NAME; for example, \\CYRUS\Pickup Holding, because for some reason some of the older servers are named after my boss’s dead cats.
When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when \\CYRUS\Pickup Holding failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding would work fine. This was super annoying.
The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008 finally retires this ancient technology by default, however, so I had two choices: I could either install the WINS server role on SBS 2008, or I could just figure out how to get the 015 DNS Domain Name option from DHCP to relay through the VPN connection.
I chose the latter option, since it’s certainly less confusing to be able to say to someone in the future “we don’t use WINS, DNS does everything.” So here’s how to do it:
1.On the SBS 2008 server, click Start > Administrative Tools > Routing and Remote Access.
2.In the tree view, drill down past the server name to IPV4 > General. Right-click the General option and choose “New Routing Protocol” and choose DHCP Relay Agent.
3.Now right-click the newly appended “DHCP Relay Agent” node and choose Properties. Add the IP address of your DHCP server (which is probably your SBS server itself), and click OK. Then click it again and choose “New Interface” and add the “Internal” interface.
4.Now if you connect through VPN, an ipconfig /all should show your domain name as a “Connection-specific DNS suffix” and pinging machines by their suffix-less computer names should work. (If it doesn’t, make sure your DHCP server is using that 015 DNS Domain Name option, which the SBS 2008 wizards set up by default.)
Monday, August 17, 2009
WARNING: IE Security update KB963027 Breaks Companyweb (SBS2003)
Companyweb requires login but doesn't work.
The issue is that that you are prompted for credentials
(user/password) that will not be accepted under any conditions.
reguardless of what account you use.
One solution is to removing IE 7 Security update KB963027,
And then companyweb can be accessed again.
The issue is that that you are prompted for credentials
(user/password) that will not be accepted under any conditions.
reguardless of what account you use.
One solution is to removing IE 7 Security update KB963027,
And then companyweb can be accessed again.
Friday, August 14, 2009
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: ]
MSSQL$MICROSOFT##SSEE Event Error 18456 on your SBS2003 server.
This issue is generally related to WSUS 3.0 that uses Windows Internal Database (MSSQL$MICROSOFT##SSEE), and the event is logged because the permissions is not correctly set for 'NT AUTHORITY\NETWORK SERVICE' on the SUSDB database file, or the MSSQL$MICROSOFT##SSEE instance.
The suggestions are to check NTFS permission on the SUSDB, and grant login permission to 'NT AUTHORITY\NETWORK SERVICE' on the instance. To do so:
1. Check NTFS permission on the SUSDB folder:
------------------
a. Locate the SUSDB.mdb on the WSUS server. By default, it is under the UpdateServicesDbFiles folder such as C:\WSUS\UpdateServicesDbFiles\SUSDB.mdf.
b. Check the Security Permissions on the C:\WSUS\UpdateServicesDbFiles folder, and grant 'NT AUTHORITY\NETWORK SERVICE' Full Control permission
2. To grant 'NT AUTHORITY\NETWORK SERVICE' login permission on the instance:
----------------
a. Open a Command Prompt on the SBS2003 server, then run the following commands:
osql -E -S servername\Microsoft##SSEE
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE'
Note: Replace servername with the host name of the SBS2003 server
b. Restart the Microsoft##SSEE service, and update service.
This issue is generally related to WSUS 3.0 that uses Windows Internal Database (MSSQL$MICROSOFT##SSEE), and the event is logged because the permissions is not correctly set for 'NT AUTHORITY\NETWORK SERVICE' on the SUSDB database file, or the MSSQL$MICROSOFT##SSEE instance.
The suggestions are to check NTFS permission on the SUSDB, and grant login permission to 'NT AUTHORITY\NETWORK SERVICE' on the instance. To do so:
1. Check NTFS permission on the SUSDB folder:
------------------
a. Locate the SUSDB.mdb on the WSUS server. By default, it is under the UpdateServicesDbFiles folder such as C:\WSUS\UpdateServicesDbFiles\SUSDB.mdf.
b. Check the Security Permissions on the C:\WSUS\UpdateServicesDbFiles folder, and grant 'NT AUTHORITY\NETWORK SERVICE' Full Control permission
2. To grant 'NT AUTHORITY\NETWORK SERVICE' login permission on the instance:
----------------
a. Open a Command Prompt on the SBS2003 server, then run the following commands:
osql -E -S servername\Microsoft##SSEE
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE'
Note: Replace servername with the host name of the SBS2003 server
b. Restart the Microsoft##SSEE service, and update service.
Wednesday, August 12, 2009
How to Restore the Windows Logo Screen Saver Back in Windows 7
How to Restore the Windows Logo Screen Saver Back in Windows 7
http://www.sevenforums.com/tutorials/7226-windows-logo-screen-saver-restore.html
http://www.sevenforums.com/tutorials/7226-windows-logo-screen-saver-restore.html
Monday, August 10, 2009
Known issues in Worry-Free Business Security (WFBS) Standard / Advanced 6.0
Known issues in Worry-Free Business Security (WFBS) Standard / Advanced 6.0
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
Find Dell Current Server PC and Laptop Deals
These are not Paid Links (I get no Commission)
Just Posted here for a quick link to Dell Deals
Current Dell Deals:
Server - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-servers?c=us&cs=04&l=en&s=bsd
Desktop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-desktops?c=us&l=en&cs=04
Laptop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-laptops?c=us&cs=04&l=en&s=bsd&~tab=1&redirect=1
Just Posted here for a quick link to Dell Deals
Current Dell Deals:
Server - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-servers?c=us&cs=04&l=en&s=bsd
Desktop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-desktops?c=us&l=en&cs=04
Laptop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-laptops?c=us&cs=04&l=en&s=bsd&~tab=1&redirect=1
Saturday, August 08, 2009
How to Switch from 32bit to 64bit or 64bit to 32bit in IIS7
Open a Command Prompt and enter the following Command Line
To Switch from x64bit to x32bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 True
-------------------------------
To Switch from x32bit to x64bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
-------------------------------
(The above command lines should all be one line)
.
To Switch from x64bit to x32bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 True
-------------------------------
To Switch from x32bit to x64bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
-------------------------------
(The above command lines should all be one line)
.
How to allow more than 1 TS Admin Session in SBS2008
In SBS2003 you could have three admin sessions
1 at the console and 2 RDC.
this would allow you to use Shadow so two admins can view screens.
(Type Shadow in a dos box and see what it says for more information)
On SBS2008 By DEFAULT you cannot do this.
From the Run line in SBS2008 type
tsconfig.msc
Find the sections on Allow remote connections to only one.
and uncheck the box!
Then you can have your regular Two or more sessions in SBS2008
(just remeber only 1 in SBS console is allowed at a time.)
1 at the console and 2 RDC.
this would allow you to use Shadow so two admins can view screens.
(Type Shadow in a dos box and see what it says for more information)
On SBS2008 By DEFAULT you cannot do this.
From the Run line in SBS2008 type
tsconfig.msc
Find the sections on Allow remote connections to only one.
and uncheck the box!
Then you can have your regular Two or more sessions in SBS2008
(just remeber only 1 in SBS console is allowed at a time.)
Labels: SBS2008
How to Remote Manage PC's in SBS2008
In SBS2003 you could right click on the PC name on the server and click MANAGE!
On SBS2008 that feature is not visable.
On the server open "computer management"
and then from the file menu, connect to another computer.
Then you can manage the computer like before.
(I'm not talking about RDC here)
On SBS2008 that feature is not visable.
On the server open "computer management"
and then from the file menu, connect to another computer.
Then you can manage the computer like before.
(I'm not talking about RDC here)
Labels: SBS2008
Monday, August 03, 2009
Blackberry Wireless Carrier account links
====================================================
To set it up: Go to the respective carrier's site link below,
setup a new email address (keep your current carrier's email), add an
account, provide the Exchange email address, and hit next. Let it time out
when it says it can't find it, then tell it you'll set it up manually, then
set it up manually by indicating it's a corporate account using OWA, hit
next, provide the OWA address, user alias, etc.
Nextel:
https://bis.na.blackberry.com/html?brand=nextel
Sprint
https://bis.na.blackberry.com/html?brand=sprint
Verizon:
https://bis.na.blackberry.com/html?brand=vzw&locale=en
ATT/Cingular:
https://bis.na.blackberry.com/html?brand=mycingular
=================================================
-Posting information from Ace Fekay
To set it up: Go to the respective carrier's site link below,
setup a new email address (keep your current carrier's email), add an
account, provide the Exchange email address, and hit next. Let it time out
when it says it can't find it, then tell it you'll set it up manually, then
set it up manually by indicating it's a corporate account using OWA, hit
next, provide the OWA address, user alias, etc.
Nextel:
https://bis.na.blackberry.com/html?brand=nextel
Sprint
https://bis.na.blackberry.com/html?brand=sprint
Verizon:
https://bis.na.blackberry.com/html?brand=vzw&locale=en
ATT/Cingular:
https://bis.na.blackberry.com/html?brand=mycingular
=================================================
-Posting information from Ace Fekay
Labels: BlackBerry
Tuesday, July 28, 2009
How to Repair the information store Exchange 2003 with the eseutil
Repair the information store:
At a command prompt, change to the drive:\Program Files\Exchsrvr\Bin folder, where drive is the letter of the drive on which Exchange is installed. Use one of the following commands:
If you are trying to restore the mailbox store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb", and then press ENTER.
If you are trying to restore the public folder store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\pub1.edb", and then press ENTER.
At the command prompt, type eseutil /mh "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to verify the consistency information that is returned.
At the command prompt, type eseutil /d "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to defragment and to compact the database.
At the command prompt, type ISINTEG -S Server_Name -FIX -TEST ALLTESTS, and then press ENTER. Repeat this several times until it reports zero fixes and zero errors.
Mount the store.
Back up the store.
At a command prompt, change to the drive:\Program Files\Exchsrvr\Bin folder, where drive is the letter of the drive on which Exchange is installed. Use one of the following commands:
If you are trying to restore the mailbox store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb", and then press ENTER.
If you are trying to restore the public folder store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\pub1.edb", and then press ENTER.
At the command prompt, type eseutil /mh "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to verify the consistency information that is returned.
At the command prompt, type eseutil /d "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to defragment and to compact the database.
At the command prompt, type ISINTEG -S Server_Name -FIX -TEST ALLTESTS, and then press ENTER. Repeat this several times until it reports zero fixes and zero errors.
Mount the store.
Back up the store.
Labels: Exchange03, SBS2003
Monday, July 27, 2009
Remote Web Workplace Requires the Microsoft Remote Desktop Active X Control
Remote Web Workplace Requires the Microsoft Remote Desktop Active X Control
“This portion of Remote Web Workplace requires the Microsoft remote desktop Active X control. Your browser security settings may be preventing you from downloading Active X controls. Adjust these settings and try to connect again”
Option 1:
1.In IE7, go to the Tools menu.
2.Choose Internet Options > Programs > Manage add-ons.
3.Look for ‘Microsoft RDP Client Control (redist)’.
4.Click on it and then look below and click on ‘Enabled’.
If you can't find 'Microsoft RDP Client Control (redist)'
It maybe need to be re installed.
Try going into registry and deleting key
7584C670-2274-4EFB-B00B-D6AABA6D3850
Then it should prompt you into installing the active X again.
Option 2:
1.“Tools” menu > Internet Options > Advanced.
2.Now click on the Reset button at bottom to reset the IE7 settings.
3.Restart Internet Explorer and retry logging into Remote Web Workplace.
4.Download and install the Active X plugin.
Once you do that you should be able to log in to Remote Web Workplace also known as RWW.
“This portion of Remote Web Workplace requires the Microsoft remote desktop Active X control. Your browser security settings may be preventing you from downloading Active X controls. Adjust these settings and try to connect again”
Option 1:
1.In IE7, go to the Tools menu.
2.Choose Internet Options > Programs > Manage add-ons.
3.Look for ‘Microsoft RDP Client Control (redist)’.
4.Click on it and then look below and click on ‘Enabled’.
If you can't find 'Microsoft RDP Client Control (redist)'
It maybe need to be re installed.
Try going into registry and deleting key
7584C670-2274-4EFB-B00B-D6AABA6D3850
Then it should prompt you into installing the active X again.
Option 2:
1.“Tools” menu > Internet Options > Advanced.
2.Now click on the Reset button at bottom to reset the IE7 settings.
3.Restart Internet Explorer and retry logging into Remote Web Workplace.
4.Download and install the Active X plugin.
Once you do that you should be able to log in to Remote Web Workplace also known as RWW.
Wednesday, July 22, 2009
How to recover an Mailbox using Exchange Recovery Store (Exchange 2003)
Instructions Here.
http://www.msexchange.org/tutorials/Recovering-Mailboxes-Exchange2003-SP1.html
http://www.msexchange.org/tutorials/Recovering-Mailboxes-Exchange2003-SP1.html
Labels: Exchange03, SBS2003
Thursday, July 16, 2009
FYI: Do not delete Computer Groups SBS2008 WSUS 3.0
Why? the Windows SBS Console Crashes when running reports
(And Daily Weekly Reports will have Stopped)
I ran into This last week and I thought I'd post it.
Running a report I get a Crash/Error
With Error
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
In log
C:\Program Files\Windows Small Business Server\Logs\console.log
there is a "NullReferenceException"
The problem was I deleted a computer group in WSUS 3.0
I deleted the Group "Update Service Excluded Computers"
(Since I felt it didn't matter since there were no computers in that group.)
Well WRONG it does matter Make sure you have all Groups.
Unassigned Computers
Update Service Excluded Computers
Update Services Client Computers
Update Services Server Computers
Note "Update Service Excluded computer" and it should NOT be "Update
Services Excluded computer" which 'Services' is plural
If any groups are not in the list or the names are not exact same, the
report will crash.
Russ
(And Daily Weekly Reports will have Stopped)
I ran into This last week and I thought I'd post it.
Running a report I get a Crash/Error
With Error
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
In log
C:\Program Files\Windows Small Business Server\Logs\console.log
there is a "NullReferenceException"
The problem was I deleted a computer group in WSUS 3.0
I deleted the Group "Update Service Excluded Computers"
(Since I felt it didn't matter since there were no computers in that group.)
Well WRONG it does matter Make sure you have all Groups.
Unassigned Computers
Update Service Excluded Computers
Update Services Client Computers
Update Services Server Computers
Note "Update Service Excluded computer" and it should NOT be "Update
Services Excluded computer" which 'Services' is plural
If any groups are not in the list or the names are not exact same, the
report will crash.
Russ
How to restore a corrupted Windows SharePoint 3.0 Services home page
Windows SharePoint Services 3.0
Windows SharePoint Services 3.0 includes a feature that you can use to re-ghost a page. The option to re-ghost a page lets you revert to the template that does not contain any errors which is stored in the database. Follow these steps:
Start SharePoint Designer 2007.
On the File menu, click Open Site.
In the Open Site dialog box, type in the Site Name box, and then click Open.
In the Folder List dialog box, click to select, and then right-click Check-Out.
On the Edit menu, click Check-In.
Note A Green circle next to the page is displayed to indicate that the page is un-ghosted.
In the Folder List dialog box, right-click, and then click Revert to Template.
Windows SharePoint Services 3.0 includes a feature that you can use to re-ghost a page. The option to re-ghost a page lets you revert to the template that does not contain any errors which is stored in the database. Follow these steps:
Start SharePoint Designer 2007.
On the File menu, click Open Site.
In the Open Site dialog box, type
In the Folder List dialog box, click to select
On the Edit menu, click Check-In.
Note A Green circle next to the page is displayed to indicate that the page is un-ghosted.
In the Folder List dialog box, right-click
Labels: SBS2008, SharePoint 3.0
How to restore a corrupted Windows SharePoint 2.0 Services home page
Restore a corrupted Windows SharePoint Services 2.0 home page
Copy the Default.aspx file in the Windows SharePoint Services site that contains the corrupted home page, rename the copy Defaultold.aspx, and then delete the Default.aspx file. To do so, follow these steps:
Start FrontPage 2003, and then open the Windows SharePoint Services site that contains the corrupted home page.
In the Folder List, double-click the Default.aspx file.
On the File menu, click Save As.
In the Save As dialog box, type Defaultold.aspx in the File name box, and then click Save.
In the Folder List, right-click the Default.aspx file, and then click Delete.
When you are prompted to confirm the deletion, click Yes.
Create a new Windows SharePoint Services site. To do so, follow these steps:
On the File menu, click New.
In the New task pane, under New Web site, click SharePoint team site.
In the Web Site Templates dialog box, click SharePoint Team Site, and then click OK.
Under Options, type the URL of the new Windows SharePoint Services site.
For example, you can create the new site as a subsite of the site that contains the corrupted home page. If the URL of the site that contains the corrupted home page is http://ServerName/Sites/TeamSite, you can specify a URL such as http://ServerName/Sites/TeamSite/SubsiteName for your new site.
Open the new site that you created.
To do so, on the File menu, click Open Site, in the Site name box, type the URL of the new site that you created earlier in step 2, and then click Open.
In the Folder List, double-click the Default.aspx file, and then click Copy.
Change to the original site that contains the corrupted home page, right-click an empty area under the Folder List, and then click Paste.
Delete any corrupted Web Parts that are located on the Default.aspx page. To do so, follow these steps:
Connect to the home page (the Default.aspx page) of your original site in your Web browser.
Click Modify Shared Page, and then click Design this Page.
Click the down arrow next to the Web Parts that you want to delete, and then click Delete.
Click Yes when you are prompted to confirm the deletion.
Add the Web Parts that you deleted to the Default.aspx page. To do so, follow these steps:
Click Modify Shared Page, click Add Web Parts, and then click Browse.
Add the Web Parts that you want to your home page.
For example, drag the Announcements Web Part and the Events Web Part to the page.
If the Home link is missing from the top link bar, add the link to the home page back to the top link bar. To do so, follow these steps:
In FrontPage 2003, open the site (if it is not already open).
In the Folder List, double-click the Default.aspx file.
In the link bar, click add link.
In the Add to Link bar dialog box, type Home in the Text to display box, click the Default.aspx file, make sure that Default.aspx is displayed in the Address box, and then click OK.
Double-click the link bar.
In the Link Bar Properties dialog box, click the General tab, and then in the Links box, make sure that Home link appears at the top of the list.
After you finish recovering the home page, delete the Defaultold.aspx file. To do so, follow these steps:
In the Folder List, right-click the Defaultold.aspx file, and then click Delete
When you are prompted to confirm the deletion, click Yes
Copy the Default.aspx file in the Windows SharePoint Services site that contains the corrupted home page, rename the copy Defaultold.aspx, and then delete the Default.aspx file. To do so, follow these steps:
Start FrontPage 2003, and then open the Windows SharePoint Services site that contains the corrupted home page.
In the Folder List, double-click the Default.aspx file.
On the File menu, click Save As.
In the Save As dialog box, type Defaultold.aspx in the File name box, and then click Save.
In the Folder List, right-click the Default.aspx file, and then click Delete.
When you are prompted to confirm the deletion, click Yes.
Create a new Windows SharePoint Services site. To do so, follow these steps:
On the File menu, click New.
In the New task pane, under New Web site, click SharePoint team site.
In the Web Site Templates dialog box, click SharePoint Team Site, and then click OK.
Under Options, type the URL of the new Windows SharePoint Services site.
For example, you can create the new site as a subsite of the site that contains the corrupted home page. If the URL of the site that contains the corrupted home page is http://ServerName/Sites/TeamSite, you can specify a URL such as http://ServerName/Sites/TeamSite/SubsiteName for your new site.
Open the new site that you created.
To do so, on the File menu, click Open Site, in the Site name box, type the URL of the new site that you created earlier in step 2, and then click Open.
In the Folder List, double-click the Default.aspx file, and then click Copy.
Change to the original site that contains the corrupted home page, right-click an empty area under the Folder List, and then click Paste.
Delete any corrupted Web Parts that are located on the Default.aspx page. To do so, follow these steps:
Connect to the home page (the Default.aspx page) of your original site in your Web browser.
Click Modify Shared Page, and then click Design this Page.
Click the down arrow next to the Web Parts that you want to delete, and then click Delete.
Click Yes when you are prompted to confirm the deletion.
Add the Web Parts that you deleted to the Default.aspx page. To do so, follow these steps:
Click Modify Shared Page, click Add Web Parts, and then click Browse.
Add the Web Parts that you want to your home page.
For example, drag the Announcements Web Part and the Events Web Part to the page.
If the Home link is missing from the top link bar, add the link to the home page back to the top link bar. To do so, follow these steps:
In FrontPage 2003, open the site (if it is not already open).
In the Folder List, double-click the Default.aspx file.
In the link bar, click add link.
In the Add to Link bar dialog box, type Home in the Text to display box, click the Default.aspx file, make sure that Default.aspx is displayed in the Address box, and then click OK.
Double-click the link bar.
In the Link Bar Properties dialog box, click the General tab, and then in the Links box, make sure that Home link appears at the top of the list.
After you finish recovering the home page, delete the Defaultold.aspx file. To do so, follow these steps:
In the Folder List, right-click the Defaultold.aspx file, and then click Delete
When you are prompted to confirm the deletion, click Yes
Labels: SBS2003, SharePoint 2.0
Tuesday, July 14, 2009
Installing Trend Micro WFBS 6.0 Error Copying File tmplcinf.xml
Installing Trend Micro WFBS 6.0 Error Copying File tmplcinf.xml
Check to make sure file tmplcinf.xml exists in Directories.
\Program Files\Trend Micro\Security Server\PCCSRV\
\Program Files\Trend Micro\Security Server\PCCSRV\pccnt\common
\Program Files\Trend Micro\Security Server\PCCSRV\Admin
\Program Files\Trend Micro\Security Server\PCCSRV\download\pattern
If not copy it from another place and try to reinstall on the client.
Check to make sure file tmplcinf.xml exists in Directories.
\Program Files\Trend Micro\Security Server\PCCSRV\
\Program Files\Trend Micro\Security Server\PCCSRV\pccnt\common
\Program Files\Trend Micro\Security Server\PCCSRV\Admin
\Program Files\Trend Micro\Security Server\PCCSRV\download\pattern
If not copy it from another place and try to reinstall on the client.
Labels: SBS2003, SBS2008, TrendMicro
Known issues in Worry-Free Business Security (WFBS) Standard / Advanced 6.0
For Current List Go to link:
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
From Link Above!
Published: 6/9/2009 5:34 AM
--------------------------------------
The following are known issues in WFBS Standard / Advanced 6.0:
• Client Deployment and Upgrade
o Worry-Free Business Security is unable to install CSA to a Windows Vista computer using Remote Install if the Remote Registry service is not running or if the computer does not allow File and Printer Sharing through Windows Firewall.
o When remotely installing an agent to a computer running Windows XP, disable Simple File Sharing on the target computer. Also, note that you cannot use Remote Install to deploy to a computer with Windows XP Home Edition.
o To completely reinstall or upgrade CSA, you will need to restart the computer. A restart will also be necessary when updating some components, including the firewall and the proxy drivers.
o After installing CSA on a computer with IIS 7.0, you must restart the IIS service. IIS 7.0 may not work as expected with CSA, which uses the Windows Filtering Platform, until it is restarted.
o You cannot run the Autopcc.exe, the login script, and the Client Packager from a terminal session.
o You cannot run Update Now on Windows 2000 computers from a terminal session.
o When accessing a computer with CSA from a terminal session, another unnecessary instance of the PccNTMon process is created in memory on the remote computer.
o Some CSA components, such as the Trend Micro Web Protection Add-On or the TrendProtect Desktop, can be installed without CSA. These components may conflict with the CSA installation and must be removed before CSA is installed.
o To use Trend Micro Vulnerability Scanner (TMVS) to deploy the CSA, you need to run TMVS on a computer running Windows 2000 or Windows Server 2003. TMVS does not support terminal sessions.
o Real-time scan on CSA can prevent Hyper-V Manager from creating virtual machines. If you encounter this issue, configure real-time scan to exclude the storage folder for your virtual machines from scanning. Hyper-V Manager uses "C:\ProgramData\Microsoft\Windows\Hyper-V" as the default storage folder, but a different folder may be specified during virtual machine creation.
o Installing or uninstalling the CSA on Windows 7 Build 7048 or Build 7057 will cause the Network Interface Card to get an IP address through DHCP with a 169.254 prefix, no matter the IP address is configured (static or dynamic). The NIC must be disabled first before installation to prevent this issue.
• Security Server
o The Security Server sends notifications for all triggered events whenever the Trend Micro Security Server Master Service is restarted.
o The following default Security Server and Scan Server ports must not be used or blocked by other applications, such as Microsoft ISA Server and other firewalls:
- HTTP: 8059
- SSL: 4343 and 4345
o Behavior Monitoring only blocks programs in the exact path specified in the list of blocked programs.
o No plug-in programs are currently available for versions 5.1 and 6.0.
o The Security Server installation automatically checks for Microsoft Data Access Components (MDAC) 2.6 or later. If MDAC 2.6 or later is not installed, it automatically installs MDAC 2.8.
Note: MDAC installation requires a restart.
o Update agents do not roll back to a previous pattern file, even if the Security Server rolled back to a previous version. If the agent updates its components from the Update Agent, the agent pattern file is used, not the Security Server pattern file.
o If an Internet connection problem occurs during Security Server installation, the installer will keep trying to validate the Activation Code without indicating any problem.
o Web installation and Remote installation will fail if another computer on the network has the same name as the Security Server.
• Web Console
o Trend Micro recommends accessing the Web console from computers that do not have adware installed. If Hotbar or other adware is installed, ActiveX errors may occur when accessing certain console screens.
o Trend Micro recommends setting Internet Explorer to apply Medium or lower security levels when accessing the Web console. Higher security settings may block necessary ActiveX controls.
By default, Internet Explorer applies Medium-low security levels for intranet sites and Medium security levels for sites in its Trusted Sites list. To help ensure you can access the console properly, add it to the Trusted Sites list.
• Firewall
o While installing CSA, the computer could temporarily lose network connection. Some applications, such as Secure Shell (SSH), Terminal Services Client, or Remote Desktop could be affected by the disconnection. If this occurs, restart the application after installing CSA.
o The CSA firewall might conflict with other firewall applications. Trend Micro recommends uninstalling or disabling the other firewall applications.
o On VMWare clients, the CSA firewall may block all incoming packets. To address this issue, add the following value to the client's registry:
- Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\PFW
- Name: EnableBypassRule
- Type: REG_DWORD
- Data: 1
• Transaction Protector
o After Transaction Protector scans a wireless access point, it shows the "unchecked" status if a timeout occurs while trying to connect to the access point.
o Transaction Protector only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
o Transaction Protector does not support remote administration software, such as Remote Desktop.
• TrendProtect
o TrendProtect cannot start automatically when installed for the first time on a computer with Internet Explorer 7.0 and Windows XP. To manually enable TrendProtect, go to View > Toolbars > TrendProtect in the Internet Explorer menu.
o TrendProtect only supports:
- Windows 2000 Professional
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Behavior Monitoring
o Behavior Monitoring only supports 32-bit operating systems; 64-bit operating systems are not supported.
o Files without valid digital signatures that violate policies may be blocked by Behavior Monitoring. Files with valid signatures are always allowed to start.
• Trend Micro Anti-Spam Toolbar
o The Trend Micro Anti-Spam Toolbar only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Messaging Security Agent
o The Messaging Security Agent (MSA) only supports typical installations of Exchange Server 2007 that include the Hub Transport, the Mailbox, and the Client Access server roles.
o As an anti-spam solution on Exchange Server 2003, users can choose between EUQ or Junk Mail integration. If you use Junk Mail integration, install Exchange Server 2003 SP2, which includes the Intelligent Message Filter (IMF), before installing MSA.
o During MSA installation, the installer may be unable to submit passwords that have special, non-alphanumeric characters to the Exchange Server computer. As a result, you may be unable to install the MSA if the domain administrator account you are using has a complex password. To work around this issue, temporarily change the password for the domain administrator account.
o When installing MSA remotely using the Web console or the Worry-Free Business Security Advanced installer to a computer running Windows Server 2008, SBS 2008, or EBS 2008, you need to specify the built-in domain administrator account because of User Access Control restrictions. Note that for computers with other operating systems, you need an account that is in the Exchange Organization Administrators group.
o During MSA installation, the setup program adds a Windows Firewall exception on the Exchange Server computer to allow the MSA to communicate with the Security Server through port 16372.
o The MSA cannot be installed on a Windows EBS 2008 computer with the Exchange Server 2007 Edge Transport server role.
• Email Reputation Services
o Email Reputation Services (ERS) is an online hosted service and its activation takes about eight hours.
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
From Link Above!
Published: 6/9/2009 5:34 AM
--------------------------------------
The following are known issues in WFBS Standard / Advanced 6.0:
• Client Deployment and Upgrade
o Worry-Free Business Security is unable to install CSA to a Windows Vista computer using Remote Install if the Remote Registry service is not running or if the computer does not allow File and Printer Sharing through Windows Firewall.
o When remotely installing an agent to a computer running Windows XP, disable Simple File Sharing on the target computer. Also, note that you cannot use Remote Install to deploy to a computer with Windows XP Home Edition.
o To completely reinstall or upgrade CSA, you will need to restart the computer. A restart will also be necessary when updating some components, including the firewall and the proxy drivers.
o After installing CSA on a computer with IIS 7.0, you must restart the IIS service. IIS 7.0 may not work as expected with CSA, which uses the Windows Filtering Platform, until it is restarted.
o You cannot run the Autopcc.exe, the login script, and the Client Packager from a terminal session.
o You cannot run Update Now on Windows 2000 computers from a terminal session.
o When accessing a computer with CSA from a terminal session, another unnecessary instance of the PccNTMon process is created in memory on the remote computer.
o Some CSA components, such as the Trend Micro Web Protection Add-On or the TrendProtect Desktop, can be installed without CSA. These components may conflict with the CSA installation and must be removed before CSA is installed.
o To use Trend Micro Vulnerability Scanner (TMVS) to deploy the CSA, you need to run TMVS on a computer running Windows 2000 or Windows Server 2003. TMVS does not support terminal sessions.
o Real-time scan on CSA can prevent Hyper-V Manager from creating virtual machines. If you encounter this issue, configure real-time scan to exclude the storage folder for your virtual machines from scanning. Hyper-V Manager uses "C:\ProgramData\Microsoft\Windows\Hyper-V" as the default storage folder, but a different folder may be specified during virtual machine creation.
o Installing or uninstalling the CSA on Windows 7 Build 7048 or Build 7057 will cause the Network Interface Card to get an IP address through DHCP with a 169.254 prefix, no matter the IP address is configured (static or dynamic). The NIC must be disabled first before installation to prevent this issue.
• Security Server
o The Security Server sends notifications for all triggered events whenever the Trend Micro Security Server Master Service is restarted.
o The following default Security Server and Scan Server ports must not be used or blocked by other applications, such as Microsoft ISA Server and other firewalls:
- HTTP: 8059
- SSL: 4343 and 4345
o Behavior Monitoring only blocks programs in the exact path specified in the list of blocked programs.
o No plug-in programs are currently available for versions 5.1 and 6.0.
o The Security Server installation automatically checks for Microsoft Data Access Components (MDAC) 2.6 or later. If MDAC 2.6 or later is not installed, it automatically installs MDAC 2.8.
Note: MDAC installation requires a restart.
o Update agents do not roll back to a previous pattern file, even if the Security Server rolled back to a previous version. If the agent updates its components from the Update Agent, the agent pattern file is used, not the Security Server pattern file.
o If an Internet connection problem occurs during Security Server installation, the installer will keep trying to validate the Activation Code without indicating any problem.
o Web installation and Remote installation will fail if another computer on the network has the same name as the Security Server.
• Web Console
o Trend Micro recommends accessing the Web console from computers that do not have adware installed. If Hotbar or other adware is installed, ActiveX errors may occur when accessing certain console screens.
o Trend Micro recommends setting Internet Explorer to apply Medium or lower security levels when accessing the Web console. Higher security settings may block necessary ActiveX controls.
By default, Internet Explorer applies Medium-low security levels for intranet sites and Medium security levels for sites in its Trusted Sites list. To help ensure you can access the console properly, add it to the Trusted Sites list.
• Firewall
o While installing CSA, the computer could temporarily lose network connection. Some applications, such as Secure Shell (SSH), Terminal Services Client, or Remote Desktop could be affected by the disconnection. If this occurs, restart the application after installing CSA.
o The CSA firewall might conflict with other firewall applications. Trend Micro recommends uninstalling or disabling the other firewall applications.
o On VMWare clients, the CSA firewall may block all incoming packets. To address this issue, add the following value to the client's registry:
- Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\PFW
- Name: EnableBypassRule
- Type: REG_DWORD
- Data: 1
• Transaction Protector
o After Transaction Protector scans a wireless access point, it shows the "unchecked" status if a timeout occurs while trying to connect to the access point.
o Transaction Protector only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
o Transaction Protector does not support remote administration software, such as Remote Desktop.
• TrendProtect
o TrendProtect cannot start automatically when installed for the first time on a computer with Internet Explorer 7.0 and Windows XP. To manually enable TrendProtect, go to View > Toolbars > TrendProtect in the Internet Explorer menu.
o TrendProtect only supports:
- Windows 2000 Professional
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Behavior Monitoring
o Behavior Monitoring only supports 32-bit operating systems; 64-bit operating systems are not supported.
o Files without valid digital signatures that violate policies may be blocked by Behavior Monitoring. Files with valid signatures are always allowed to start.
• Trend Micro Anti-Spam Toolbar
o The Trend Micro Anti-Spam Toolbar only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Messaging Security Agent
o The Messaging Security Agent (MSA) only supports typical installations of Exchange Server 2007 that include the Hub Transport, the Mailbox, and the Client Access server roles.
o As an anti-spam solution on Exchange Server 2003, users can choose between EUQ or Junk Mail integration. If you use Junk Mail integration, install Exchange Server 2003 SP2, which includes the Intelligent Message Filter (IMF), before installing MSA.
o During MSA installation, the installer may be unable to submit passwords that have special, non-alphanumeric characters to the Exchange Server computer. As a result, you may be unable to install the MSA if the domain administrator account you are using has a complex password. To work around this issue, temporarily change the password for the domain administrator account.
o When installing MSA remotely using the Web console or the Worry-Free Business Security Advanced installer to a computer running Windows Server 2008, SBS 2008, or EBS 2008, you need to specify the built-in domain administrator account because of User Access Control restrictions. Note that for computers with other operating systems, you need an account that is in the Exchange Organization Administrators group.
o During MSA installation, the setup program adds a Windows Firewall exception on the Exchange Server computer to allow the MSA to communicate with the Security Server through port 16372.
o The MSA cannot be installed on a Windows EBS 2008 computer with the Exchange Server 2007 Edge Transport server role.
• Email Reputation Services
o Email Reputation Services (ERS) is an online hosted service and its activation takes about eight hours.
Labels: SBS2003, SBS2008, TrendMicro
Friday, June 19, 2009
Where Can I get the Microsoft Font?
I'm unsure of the license with this?
But like me when you want to use the word "Microsoft" in your Documents and you want it to look just as Cool as Microsoft does.
(Especially when you write sales flyers for the clients)
You need the Font.
The font is: Helvetica 96 Black Italic.ttf
and can be downloaded here.
http://www.sbits.biz/MicrosoftFont/
Downloaded it to your Font directory
%windir%\fonts (AKA C:\Windows\Fonts\)
and next reboot you have them.
No Warranties with this file, use at your own risk!
But like me when you want to use the word "Microsoft" in your Documents and you want it to look just as Cool as Microsoft does.
(Especially when you write sales flyers for the clients)
You need the Font.
The font is: Helvetica 96 Black Italic.ttf
and can be downloaded here.
http://www.sbits.biz/MicrosoftFont/
Downloaded it to your Font directory
%windir%\fonts (AKA C:\Windows\Fonts\)
and next reboot you have them.
No Warranties with this file, use at your own risk!
Labels: TIPS
Thursday, June 18, 2009
How to Change the CompanyWeb Timeout in SBS 2008
The CompanyWeb site in SBS 2008 is configured with a 30 minute idle timeout in the default master page. This timeout is unique to CompanyWeb in SBS 2008 and affects connections to CompanyWeb from the LAN or over the Internet. To change this timeout:
1.Create a backup of your current CompanyWeb using the native SBS backup.
2.Browse to http://companyweb.
3.Click Site Actions and then click Site Settings.
4.In the Galleries section, click Master pages.
5.Right-click default.master, point to Send To and then click Download a copy. Save the file in the My Documents or some folder of your choosing.
6.Make a backup copy of this file.
7.Open the default.master file in Notepad.
8.Locate this section:
//this value indicates after how many miliseconds
var LOGIN_SESSION_TIMEOUT_VALUE = 1800000;
function EndSession()
{
window.location = "/_layouts/SignOut.aspx";
}
9.Modify the 1800000 value to the desired timeout in milliseconds.
60000 milliseconds = 1 minute
1800000 milliseconds = 30 minutes (default)
3600000 milliseconds = 1 hour
10.In Notepad, click File and then click Save. The file should be saved as default.master and not default.master.txt. Note the MASTER File type in the screenshot below.
11.In CompanyWeb, click Upload, and select the default.master file. Leave the box Add as a new version to existing files checked and click OK. You can also specify the change you made in the comments section.
12.After the document is uploaded, click OK.
Note: It should appear in the master page gallery default.master and not default.master.txt (or any other extension).
1.Create a backup of your current CompanyWeb using the native SBS backup.
2.Browse to http://companyweb.
3.Click Site Actions and then click Site Settings.
4.In the Galleries section, click Master pages.
5.Right-click default.master, point to Send To and then click Download a copy. Save the file in the My Documents or some folder of your choosing.
6.Make a backup copy of this file.
7.Open the default.master file in Notepad.
8.Locate this section:
//this value indicates after how many miliseconds
var LOGIN_SESSION_TIMEOUT_VALUE = 1800000;
function EndSession()
{
window.location = "/_layouts/SignOut.aspx";
}
9.Modify the 1800000 value to the desired timeout in milliseconds.
60000 milliseconds = 1 minute
1800000 milliseconds = 30 minutes (default)
3600000 milliseconds = 1 hour
10.In Notepad, click File and then click Save. The file should be saved as default.master and not default.master.txt. Note the MASTER File type in the screenshot below.
11.In CompanyWeb, click Upload, and select the default.master file. Leave the box Add as a new version to existing files checked and click OK. You can also specify the change you made in the comments section.
12.After the document is uploaded, click OK.
Note: It should appear in the master page gallery default.master and not default.master.txt (or any other extension).
