Following code works with Firefox, Chrome -moz-border-radius: 20px; -webkit-border-radius: 20px;

For IE9 use the following code border-radius: 20px;

If you want to have only one rounded corner on the HTML, I found the following nice [...]]]> If you are looking into adding rounded corners to HTML elements, you can use the following CSS properties.

Following code works with Firefox, Chrome

-moz-border-radius: 20px;
-webkit-border-radius: 20px;


For IE9 use the following code

border-radius: 20px;


If you want to have only one rounded corner on the HTML, I found the following nice website which allows you to change rounded corners as you wish. Full credit to the website’s owner / developer
http://border-radius.com

There are plenty of forums out there concentrating [...]]]> I was having the DHCP server fail to see active directory with error number 1059, where I was unable to authorize the DHCP server for IP address leasing. I have parent – child domain environment where I was trying to deploy DHCP server in the child domain.

There are plenty of forums out there concentrating on networking side, but I was installing the DHCP server on the child domain DC. Therefore, there should not be any networking and firewall issues. I even tried DCDIAG.exe and LDP.exe with pass as the end result.

Note:  There is no need to disable IPv6 as Microsoft says that in Windows server 2008 and windows server 2008 R2, IPv6 does play some role in the proper working of the server.

Solution: My network connectivity and DCDIAG.exe tests passed with flying colors.  After further investigation the solution was to add the “administrator” account of child domain to the “enterprise administrators” group in the forest. That means simply log on the parent DC and add the CD administrator to the group. After restarting the DCHP service on the Child DC everything started working as it should be.

So, network connectivity, DNS are not the only factors. We have to look into permissions as well so that the Child DC can authorize the DHCP in AD.

Hope this post will come handy to admins just like me.

Thanks for reading.

Now this is my solution which involves [...]]]> Since upgrading to Adobe reader X, I am having problems previewing and opening pdf attachments within the Microsoft outlook 2010.  Searching through Adobe’s own forums and internet was waste of time as still it needs to be solved. you can access the topic at the following link: http://forums.adobe.com/message/3363074?tstart=1.

Now this is my solution which involves uninstalling Adobe reader X and reinstalling the older Adobe 9 version.

1. First go to Add or remove programs (windows xp) or programs and features (windows vista or windows 7).
2. Uninstall the Adobe reader X.
3. Restart your computer.
4. Download Adobe acrobat 9 from the following Adobe URL: http://get.adobe.com/reader/otherversions/.

Once Adobe reader 9 was installed, I was able to open and preview a all my pdf attachments in Microsoft outlook 2010.

Hope you find the topic helpful and thank you for reading.

Errors

Make sure the option “Ignore other applications that use Dynamic Data Exchange [...]]]> If you came across the following errors from Microsoft excel 2010 while opening files either saved on your computer or as an email attachment

Errors

1. Cannot open file. check whether the path is correct or file exists
2. Cannot send command to the file.

Make sure the option “Ignore other applications that use Dynamic Data Exchange (DDE).” in excel setting is not checked. Please  see the step by step to uncheck the option.

1. Click on File–>Options

2. click on advanced and on the right hand side pane scroll down and look for the option as shown below. Make sure the highlighted option is unchecked in your excel 2010 copy

3. Restart excel

4. All files will be able to open when clicking on them

Thank you for reading and please leave comments or suggestions.

During Microsoft outlook 2010 start up I noticed that the outlook is processing quiet a few COM addins before [...]]]> My Microsoft outlook 2010 was playing up during start ups. Most of the time during send and receive of the emails it use to freeze and I have to end the process in the Task manager.

During Microsoft outlook 2010 start up I noticed that the outlook is processing quiet a few COM addins before the window appears. COM addins such as Microsoft Exchange, Microsoft SharePoint, Outlook connector for Hotmail, Antivirus and anti spam addins. All these addins were somewhat were impacting my outlook start up and I was sure that they must be responsible for frequent freezing my outlook was experience.

So, to troubleshoot I need to disable some of the addins which I don’t require and see if there are some improvements in my Microsoft outlook 2010. After disabling some addins the outlook was more responsive and so far I have not experience any freezing since I have disabled the addins which were not required for my purpose.

Please see below step by step on how to disable outlook addins

1. Click File and then options
   
2. On the Outlook options dialog box click on Add-Ins as shown in the image below
   
3. Click “Go” on the bottom of the dialog box and you will be presented with another dialog box as shown below. Uncheck all the addins which you want to disable and press ok. Restart your outlook and hopefully you may find improvements in loading of Microsoft outlook 2010.
   

I hope you find my post helpful. Please leave comment or suggestion and thank you for reading.

I guess there are two solutions for the issues which are detailed as follow. The common ground for both solutions [...]]]> This error message “cannot create file” in outlook 2010 has given me pain for quiet a while now. During my searching in Google I came across the solution from Microsoft at the following link: http://support.microsoft.com/kb/305982.

I guess there are two solutions for the issues which are detailed as follow. The common ground for both solutions is opening the registry and looking up for the outlook temp folder path where is saves attachments  as a security measure.

The reason I am reading in plenty of other forums and Microsoft tech net website is that outlook throws an error if rename count of the file reaches 99. I hope this will be fixed in future releases of Microsoft outlook.

This will work for other versions of Microsoft outlook where you need to click the relevant version folder in the registry.

SOLUTION 1 (Delete the files in the existing temp folder)

1. Open registry on your computer by typing “regedit” in run dialog box (Win+R)

2. Navigate to “HKEY_CURRENT_USER\Software\Microsoft\Office\<<Your Office suite version>>\Outlook\Security\”

3. On the right side double click “OutlookSecureTempFolder”.

4. Copy the path in the text box.

5. Paste the copied path in “OutlookSecureTempFolder” in run command box and press enter.

6. Select all and delete the files.

7. Restart your outlook.

SOLUTION 2 (Change the path of Microsoft outlook temp folder)

1. Create a folder in your C drive and name it “outlook_tmp“. Copy the path of the folder “C:\outlook_tmp”

2. Open registry on your computer by typing “regedit” in run dialog box (Win+R)

3. Navigate to “HKEY_CURRENT_USER\Software\Microsoft\Office\<<Your Office suite version>>\Outlook\Security\”

4. On the right side double click “OutlookSecureTempFolder”.

5. Delete the path in the text field and paste the previously copied path in the text field.

6. Press OK and exist out of the registry.

7. Restart the computer.

8. I guess if same problem reoccurs we can simple go to the C:\outlook_tmp folder and delete the files.

Hope this will help. Thank you for reading.

Go to C:\Windows\System32\sysprep\sysprep.exe and double click on the file to start the sysprep tool as shown below.

Once sysprep will finish its processing it will [...]]]> If you are experiencing SID issues for Windows server virtual machine, then sysprep tool in windows 2008 R2 can save you time and might as well your bacon.

Go to C:\Windows\System32\sysprep\sysprep.exe and double click on the file to start the sysprep tool as shown below.

Once sysprep will finish its processing it will shutdown the windows 2008 R2 copy which can then be used as base image for importing new Virtual machines.

If you are looking for troubleshooting Exchange 2010 SP1 management console error, please click on the following link EMC error

The following error occurred when retrieving user information for ‘Domain\administrator’:

The operation couldn’t be performed because object ‘S-1-5-21-…….’ couldn’t be found on ‘DC.domain.local’. It was running the command ‘Get-LogonUser’.

I will start with little [...]]]> It took me nearly a week to find a solution for the following error message in exchange 2010 SP1 management console:

The following error occurred when retrieving user information for ‘Domain\administrator’:

The operation couldn’t be performed because object ‘S-1-5-21-…….’ couldn’t be found on ‘DC.domain.local’. It was running the command ‘Get-LogonUser’.

I will start with little background on my test lab. I am running virtual box 4.04 on my windows 7 64 bit machine as host computer. I have 2 virtual machines both with windows 2008 R2 Ent installed. One VM is the DC for the test lab domain and the other VM is used to installed exchange 2010 SP1 typical installation.

Both VMs are setup with “Internal Network” so that they can talk to each other. Now, I believe everyone would have taken the advantage of “Export Appliance” and “Import Appliance” feature of Virtual box 4.04. This saves you time of reinstalling the OS where you can simply import the VM and change the setting as per the requirements of the new VM.

But beware when you are trying to install servers on VM using the “Import Appliance” feature. The drawback to this method is the VMs will have the same SID which cause the problem in server applications such as exchange 2010 etc. But there is a solution to this problem by performing sysprep on the original VM installation and export that VM so that when imported to new VM and started for the first time it will generate a new SID as if the server OS is installed on a new hardware.

How to Sysprep Windows 2008 R2 server

Detailed instruction on how to sysprep Windows 2008 R2 can be found in the following blog: Sysprep windows 2008 R2

SOLUTION

Important note

Make sure to backup your exchange database files before deleting the original exchange 2010 virtual machine.

You can delete the exchange 2010 SP1 virtual machine where you are experiencing the issue. As we will be restoring the exchange 2010 server on our new syspreped virtual machine. All the exchange information is stored in AD on your domain controller except for receive connectors which have to be manually created once the restoration of exchange 2010 is successful.

1. Import syspreped VM using the “Import Appliance” feature of Virtual box and created a new VM. Please see the section “How to Sysprep Windows 2008 R2 server” on how to sysprep windows virtual machine and export it for future use.
2. Follow the instruction on how to prepare Windows 2008 R2 VM to restore exchange 2010 SP1 server in my other blog “Recovering Exchange Server 2010“.
3. Once the above steps are completed you can now restore your exchange database and create new connectors.

I hope this blog will be helpful. Thank you for reading.

Thanks to new Vbox 4 (http://www.virtualbox.org/) I was able to export and import fresh copy of my Windows [...]]]> Last night I was playing with my Exchange 14 virtual machines and thought of a disaster scenario and how to recover it if it happened in real world with one of my clients. So here it goes.

Thanks to new Vbox 4 (http://www.virtualbox.org/) I was able to export and import fresh copy of my Windows 2008 R2 server evaluation version virtual machine. Off course my original Exchange 14 typical installation virtual machine was off and disconnected to mimic the disaster. Few important points that require attention before starting the restore process for Exchange 2010.

1. Make sure to reset the account in the Computers OU of your test DC as shown in the image below
   
   
2. Make sure to install the same OS on the new virtual machine as it was on original Exchange 2010 server was needs recovery.
3. Make sure to rename the newly installed Windows 2008 R2 server exactly the same as your original Exchange 2010 server.
4. Make sure to use the same Exchange DVD or ISO version that was used during the original Exchange 2010 installation. Everyone must be keeping the DVDs or ISO backup Right!!!
5. New Virtual machine should have same IP address as the original one.

Once all the above points are met and all the prerequisites are installed for the typical installation of the Exchange 2010 which are

1. Microsoft Office Filter Pack 2007 or 2010
2. All the required roles are installed on the server where exchange 2010 will be recovered.
   Import-Module ServerManager
   Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart

Now open elevated command prompt on the new Windows 2008 R2 server and mount the ISO or DVD of Exchange 2010 server to the new Virtual machine. Enter the following command

1. Change directory on the command prompt to your DVD drive in Virtual machine.
2. Type Setup.com /M:RecoverServer /DoNotStartTransport . Use the the /DoNotStartTransport if recovering Hub or Transport roles on the server. With this switch you will be able to restore the transport queues before putting the server in production.
   

This process took some time to complete but the final word was that I was able to use the previously installed Exchange after recovering it from the disaster.

Please note the above steps are general overview of the Exchange 2010 recovery. Every environment is different so please check Microsoft Technet website before performing the above steps for more information that fits your Exchange environment.

Thanks for reading