18 Sept 2012

EMC does not start


EMC has error when launching
The attempt to connect to http://exch01.domain.local/powershell using "KERBEROS" authentication failed: connecting to remote server failed with following error message: access is denied

1. Check all services make sure they are all started
2. Check the time and time zone, make sure it synchronized with DC

Lauch EMC, if it still does not work go to the next steps

3. From exchange server open a command prompt and type
WinRM QuickConfig
Answer "y" or yes to all prompts.
Keep running the above command until it returns a positive result.
(WinRM already set up to receive......blah, blah, blah)
4. After that returns a similar message as above, set they are set to start Default
Windows Remote Management (WS-Management)
World Wide Web Publishing Service.

5. Run IIS Manager. Click on the "Default Site" and select restart

Good luck 

10 Sept 2012

Tip: 7 Best Practices for Physical Servers Hosting Hyper-V Roles

http://technet.microsoft.com/en-us/magazine/dd744830.aspx


Before setting up a physical server to host the Hyper-V role, download, read, and understand information included in the white paper “Performance Tuning Guidelines for Windows Server 2008”. Three sections in this white paper that can have a significant impact on the performance of the physical server discuss tuning the server hardware and setting up the networking and storage subsystems. These are especially critical for Hyper-V because the hypervisor itself sits on top of the hardware layer as described earlier and controls all hardware in Windows Server 2008. The operating system itself essentially runs in a virtual machine, better known as the Parent Partition.

Here are seven best practices for physical servers hosting the Hyper-V role.

Avoid Overloading the Server
Determining the number of virtual machines that will be hosted on the Hyper-V server and the workloads they will be handling is critical. The version of the operating system that will be installed on the physical server can help in this regard, so the first “best practice” is to consider using Windows Server 2008 Datacenter x64 with Hyper-V. The Datacenter x64 edition supports up to 64 processors, 2 terabytes of physical memory, and 16 failover cluster nodes for Quick Migration scenarios and allows unlimited virtual machines to be run in Hyper-V. Selecting a Server Core installation provides added benefits, including enhanced security and lower maintenance.

Ensure High-Speed Access to Storage
For storage, consider using a storage area network (SAN) that is configured with highspeed (10,000 rpms or greater) drives (SATA or SAS) that support queued I/O and Raid 0 +1 configurations. You can use either Fibre Channel or iSCSI SAN hardware.

Install Multiple Network Interface Cards
For networking, be sure to have more than one network card installed on the physical server and dedicate one network interface to Hyper-V server administration. This means no virtual networks in Hyper-V will be configured to use this NIC. For high-workload virtual machines, you might want to dedicate a physical network adapter on the server to the virtual network the virtual machine is using. Ensure virtual machines that share a physical adapter do not oversubscribe to the physical network. Use the Reliability And Performance Monitor to establish a performance baseline for the load and then adjust NIC configurations and loads accordingly.

If you have only a single NIC in the machine that you are configuring the Hyper-V role on and you are doing the configuration remotely (say, in an RDP session) if you choose to bind the Virtual Switch Protocol to the single NIC in the machine, you will be disconnected from your session and a reconnection might not be possible until the newly created virtual network adapter has been properly configured.

Avoid Mixing Virtual Machines That Can Use Integration Services with Those That Cannot
Do not mix on the same physical server virtual machines that can take advantage of Hyper-V Integration Services with those that cannot. Virtual machines that cannot use Integration Services must use legacy network adapters to gain access to the physical network. To accommodate legacy network adapters, you might need to disable some high-end features on the network interface, which can unnecessarily limit the functionality of the synthetic devices. Additionally, using emulated devices places an extra workload on the Hyper-V server.

Configure Antivirus Software to Bypass Hyper-V Processes and Directories
If you are running antivirus software on the physical server, you might want to consider excluding the Vmms.exe and Vmswp.exe processes. Also, exclude the directories that contain the virtual machine configuration files and virtual hard disks from active scanning. An added benefit of using pass-through disks in your virtual machines is that you can use the antivirus software running on the physical server to protect that virtual machine.

Avoid Storing System Files on Drives Used for Hyper-V Storage
Do not store any system files (Pagefile.sys) on drives dedicated to storing virtual machine data.

Monitor Performance to Optimize and Manage Server Loading
When running multiple high-workload virtual machines on a Hyper-V server, ensure a proper aggregate performance baseline is obtained over a specified period of time (say, five days during normal working hours) to ensure the hardware configuration for the physical server is optimal to support the load being placed on it by the virtual machines. If adding more memory, processors, or higher performing storage is not possible, you might need to migrate the virtual machines to other Hyper-V servers.

9 Sept 2012

Raid 10 on x3650M4 with ServerRaid M5510e



It will be easier if raid setup can be done in ServerGuide but unfortunately at the time I was writing this post ServerGuide 9.23 did not work with my x3650 M4 7915.

1. Turn on the server and press F1 at the IBM startup screen.

2. Select Server Settings - Adapter and UEFI drivers then press Enter (to compile the list of drivers)


3. Select the type of Raid card which is in your server

4. You will have 2 options EFI WebBios and EFI CLI . Select option 1 EFI WebBios


5. Select your raid card and click Start

6. Select Configuration Wizard at MegaRaid Bios Config Utility screen.
7. Select New Configuration then Manual Congiguration and click Next
8. Select DriveGroup0 on the right pane (DriveGroups) and select half of physical disk on the left pane (Drives) and click Add to Array.
9. Click Accept DG. MegaRaid will display another drive group DriveGroup1

10. Select new DriveGroup1 on the right pane then select the rest hard disk on the left pane and click on Add to Array.
11. Click Accept DG. In the right pane you will have 3 drivegroups but only 2 has size displayed. The size of dirvegroup is the size of your hard disk.

12. Click Next.

13. In the Span Definition screen select each of DriveGroup in the combo box and click Add to Span.
14. Click Next.
15. If the type of Raid is 10 that means you do thing right. Click Update Size and then Accept.

16. The next screen will display Raid level of every drivegroup. In my case it is Raid0.

17. Click Next then Accept to finish

Good luck :-)

ServeRaid M5110e on x3650M4

Unfortunately at the time I am installing Windows 2008 R2 on x3650M4 (7915) IBM has  not yet updated ServeRaid M5110e on its ServerGuide 9.23. Whatever raid level I selected by following steps in ServerGuide the critical error of raid update failure displayed. It takes me a day before  realizing that I need to find a way round.
First of all the raid setting have to be done via WebRaid because ServerGuide raid setup did not work.
Secondly find out RaidServe M5110e windows driver at http://download2.boulder.ibm.com/sar/CMA/XSA/ibm_dd_sraidmr_5.2.127_windows_32-64.exe and copy it in to USB key
Lastly restart 3650M4 by Windows 2008 R2 DVD and setup as normally except had to upload ServeRaid driver from the USB key before able to see the hard disk partition.
...Go for a beer now

Total Pageviews