Monthly Archive: September 2012

Sep 29 2012

HP Proliant ML350e Gen8 Server has no SmartStart CD

With all HP Servers there would be a SmartStart CD that ship with the server. So you will unpack the server, complete the hardware configuration and then boot from the SmartStart CD. Once booted from the SmartStart CD, you will create your array configuration and then install your Operating System.

I received a HP ML350e Gen8 server that I need to configure and install for a client. I opened the box and was surprised not to find a SmartStart CD. The only CD in the box is a HP Documents CD with HP Support Documents on it. I could not understand how HP could forget to give me a SmartStart CD.

I decided to have a quick look at the HP Documents CD to try and figure out what is going on. On the CD I found a document called “Setup Poster” and this is where I found the answer.

HP went one step further with their 8th Generation Proliant Servers. The SmartStart CD is now integrated in the boot process so there is more CD to boot from. HP calls this the Intelligent Provisioning.

Here are the steps I took:

 

  1. Booted the HP ML350e Gen8.
  2. Halfway through the boot cycle there will be an option to press F10 to access Intelligent Provisioning.
  3. When the application has loaded, complete Step 1 and Set Intelligent Provisioning Preference.
  4. Then on the Home Screen, click Performance Maintenance.
  5. In the Performance Maintenance you can complete the Software Update and Firmware Update.
  6. You also need to open the Array Configuration Utility and setup your Array Configuration.
  7. Then go back to the Home Screen and click on Configure and Install.
  8. Once in the Configuration and Install screen, follow the prompts and select the Operating System that you want to install.
  9. You will be asked to insert the Operating System disk that you want to install.
  10. Now you will go through the process of installing the Operating System and configure your server.

The Intelligent Provisioning is a very helpful and easy application to use and with the fact that it is built into the server BIOS makes for much easier usage. The HP Proliant ML350e G8 and all other new Generation 8 Proliant Server use the Intelligent Provisioning. Well done HP!

Here is the Setup Poster as per the HP Document CD.

HP Proliant ML350e Gen8 Server has no SmartStart CD

Sep 25 2012

The Trust Relationship between this Workstation and the Primary Domain failed

Since Windows 7 is in production a new error had shown up and I never found the real workaround.

If you had the error message “The Trust Relationship between this Workstation and the Primary Domain failed” when you tried to logon you will know what I’m talking about.

Most of the time I receive this error when the workstation is connected to a domain and you do a System Restore. I also had it before after certain Windows Updates. As soon as the workstation reboot after the System Restore or Windows Update you will get this error and then you won’t be able to logon with your domain user and password. Next you will realise that the Local Administrator Account on the workstation is disabled by default in Windows 7 so if you haven’t setup an Local User or enabled the Administrator Account you have yourself a little problem.

The Trust Relationship between this workstation and the Primary Domain failed

 

Here is how I normally fix the issue:

First if you don’t have a Local Account to login to, disconnect the workstation from the network by removing the network cable. Now reboot the workstation into Safe Mode and login with the Domain Username and Password that is known to you. Next enable and reset the Local Administrator Account’s password and reboot and login with the Local Administrator.

When logged in with the Local Administrator Account or Local User with Administrator Rights, make a backup of the User Folder (C:\Users\<username>).

Then remove the workstation from the domain and reboot. When the reboot is done, log back in with your Local User with Administrator Rights.

Open REGEDIT (START -> RUN -> REGEDIT) and browse to the following Registry Key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\

In the “ProfileList”, search for the profile that you can’t login to anymore and remove the Profile from the ProfileList.

Reboot the workstation and again log in with your Local User with Administrator Rights. Re-join your workstation to the domain and reboot again. Now, logon with the domain user that you were unable to logon with before.

After the new profile for the Domain User has been configured in Windows 7, restore the backup that you made of User Folder by copying all the files back to the profile (Documents, Desktop and Favourites etc.)

This always solves the error “The Trust Relationship between this workstation and the Primary Domain failed”. If you have any other solution or a quicker fix for this, please inform me.

Sep 24 2012

Internet Explorer Warning: Security Update MS12-063

If you are an Internet Explorer user like me, be warned! Microsoft Corp discovered a bug in Internet Explorer (all versions) that makes your Operating System vulnerable to attacks by hackers. They released the warning on 17 Sept 2012 and urged all customers to download the security update available on Microsoft’s website.

There are millions of Internet Explorer users around the world that might be affected so rather be safe than sorry and run your Windows Updates to get the Security Update. Microsoft also released a free tool, known as Enhanced Mitigation Experience Toolkit or EMET, which is available from Microsoft’s website. You will have to configure it manually.

Alternatively you can download Security Update MS12-063 (KB 2744842) and install it manually. This Update was released by Microsoft on 21 Sept 2012 and don’t need any configuration. Make sure you download the correct Update for the version of Internet Explorer that you are using.

Take the following security measurements to protect yourself against hackers:

–          Make sure Automatic Windows Updates is enabled on your PC.

–          Make sure you have a good Anti-Virus and that it is updated with the latest Anti-Virus definition.

–          Check in your Add/Remove Programs that you don’t have any malicious software installed.

–          Stay away from websites that asks you to install browser add-ons.

–          Alternatively you can use another Internet Browser like FireFox, Google Chrome and Opera.

 

To ensure your Windows Updates is enabled, see Microsoft Knowledge Base Article 294871.

Sep 20 2012

Disable password complexity on Server 2008 and Server 2011

Every single time I install a new server for a client I have to go through these steps to change or disable password complexity on server 2008 and server 2011. When you install the new server software, the default Password Policy is set to the following:

–          Enforce password history                                             24 passwords remembered

–          Maximum password age                                              42 days

–          Minimum password age                                               1 days

–          Password must meet complexity requirements       Enabled

–          Store passwords using reversible encryption           Disabled

Now don’t get me wrong, these settings as set by default by Microsoft is not a bad thing. These days you can’t have secure enough passwords anymore. I on the other hand like to set a password according to a password standard that we have in my company. The password is then set according to the client’s need together with my company password policy which include special characters and so on e.g. @@companyname@@001! (This is only an example and not the actual company password policy we use)

So when we then install the new server software, we change the Administrator password immediately according to what we want it.

Here is how to disable the password complexity on Server 2008 and Server 2011 so that you can put in the password that you want:

Go to START -> ADMINISTRATIVE TOOLS and open GROUP POLICY MANAGEMENT.

Disable password complexity on Server 2008 and Server 2011

Browse down in the FOREST until you get to DEFAULT DOMAIN POLICY under your network domain name.

Disable password complexity on Server 2008 and Server 2011

Right-click on DEFAUL DOMAIN POLICY and click EDIT.

Disable password complexity on Server 2008 and Server 2011

On the right hand side double-click on PASSWORD MUST MEET COMPLEXITY REQUIREMENTS.

Disable password complexity on Server 2008 and Server 2011

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In the next window, select DISABLE and click OK

Now you can go to Active Directory Users and Computers and change your Administrator Password to whatever you want to without any password restrictions.

Sep 18 2012

Blackberry Enterprise Server and Exchange 2010: OpenMsgStore failed (8004011d)

As promised in my previous Blackberry Enterprise Server article, here is the solution for the OpenMsgStore failed (8004011d) that you might receive in the Windows Event Log.

When you follow the BESx 5.0.x installation guide you would have been told to run the following commands on in your Microsoft Exchange Management Shell.

New-ThrottlingPolicy BESPolicy

Set-Mailbox “BESAdmin” –ThrottlingPolicy BESPolicy

When you run these two commands it would have created a new policy and added BESadmin with all the default setting (RCAMaxConcurrency – 20) to your Exchange 2010 server. This will not prevent the “OpenMsgStore failed (8004011d)” error especially if you add multiple users to your BESx server.

Here are the commands that you need to run in the Exchange Management Shell:

1.  You need to change the RCAMaxConcurrency to unlimited. The default setting is 20.

Get-ThrottlingPolicy | where {$_.IsDefault –eq $true} | Set-ThrottlingPolicy –RCAMaxConcurrency #null

2.  Run the following command to display a list of your Throttling Policies.

Get-ThrottlingPolicy

3.  From the output of the above command, locate and copy the DefaultThrottlingPolicy” name.

Example: “DefaultThrottlingPolicy_a1f84187-7a42-4ece-9276-06c704be21e7”

4.  Enter and run the command below with your DefaultThrottlingPolicy name pasted into the command.

Set-Mailbox “BESAdmin” –ThrottlingPolicy <Default Policy Name>

Example: Set-Mailbox “BESAdmin” DefaultThrottlingPolicy_a1f84187-7a42-4ece-9276-06c704

5.  After you have completed the above steps you need to remove the “BESPolicy” that is not required anymore.

Remove-ThrottlingPolicy BESPolicy

When you have completed the above steps successfully, the OpenMsgStore failed (8004011d) error in the Event Log should be gone for good and your Blackberry Enterprise Server should be running as normal.

Page 1 of 212