RSS

Installing Server 2003 (R2) x64 on a Dell PowerEdge with a Perc5i controller including pitfalls and how to avoid them

When installing Windows 2003 x64 on a Dell with Perc5/6 controller using DRAC virtual media you may encounter the following issues:

  1. The default windows installation media does not contain the drivers for the raid controller. As a result disks will not be visible during setup and you will not be able to install Windows.
  2. The Windows 2003 install does not contain the drivers for the raid controller. As a result disks will not be visible during setup and you will not be able to install Windows.
  3. By putting the standard Dell Perc5/6 Windows 2003 x64 drivers on a (virtual) floppy and pressing F6 during Windows setup the drivers will not be detected, the raid controller and disk will still not be visible and you will not be able to install Windows. PS: For creating a virtual floppy an easy to use program is winimage.
  4. Even though you integrate the standard Dell Perc5/6 Windows 2003 x64 drivers into the installation media using nLite, the raid controller and disk will still not be visible and you will not be able to install Windows.
  5. When installing by using DRAC virtual media, the first setup part (text-mode) will complete. After the first reboot however, you will get an error stating something like the files or cdrom cannot be found or please insert the cd-rom containing the files.

The solution lies in the following actions:

  1. Download the drivers from Dell.
  2. Replace the content of txtsetup.oem as described here: http://www.msfn.org/board/topic/120461-issues-with-txtsetupoem/
  3. Extract the Windows Server 2003 x64 files to a temporary folder on your disk. Make sure that hidden/system files are copied as well.
  4. Use nLite to integrate the driver and create a new ISO. Beware, some virus scanners might block some files. So please check your anti-virus activity to see if no files have been blocked since this could result in an image that is not working.
  5. When installing from DRAC, disable the physical CD-rom in the bios since Windows setup will only check the first CD-rom drive. Otherwise you will get an error that the files/cd-rom cannot be found. A similar issue might also occur when you are installing using the physical cd-rom, then you would need to disable the virtual cd-rom.

Alternative method using a flash drive:

http://thebackroomtech.com/2008/03/13/a-dell-poweredge-server-windows-2003-x64-and-the-battle-over-sas-raid-drivers/

Alternative method using the Dell Systems Build and Update Utility (SBUU)

For installing, you can also use the Dell Systems Build and Update Utility (SBUU). For more information, including a video check:
http://en.community.dell.com/techcenter/systems-management/w/wiki/1765.aspx

Keep in mind however that you might get errors stating that the file/cd cannot be found when you are installing. If this is the case, try disabling either the virtual cd-rom or the physical cd-rom depending on the installation method you’re using.

The reason I did not use this method, is because I was trying to restore a failed system instead of simply performing an initial install.

Tip for when you need to create x86 installation media (not x64):

You can download existing mass storage driver packs instead and integrate them using nLite. Unfortunately these are not available for x64. A tutorial can be found here. Beware, some virus scanners might block some files. So please check your anti-virus activity to see if no files have been blocked since this could result in an image that is not working.

Tip for when you want to create create restore/recovery media:

Sometimes just creating installation media is not enough. Sometimes you need to be able to recover data from existing servers that cannot boot or simply perform a chkdsk or to replace/edit a file. In this case you can create a bootcd like by example BartPE. You  can use the driver packs mentioned above to make sure it will recognize a lot of raid controllers or even HBA’s. You can also install plugins to by example create/restore image backups or to perform data recovery. Some of these plugins can be found here.

 
Leave a comment

Posted by on April 24, 2012 in Uncategorized

 

Microsoft Skydrive improved, but freely available space decreased from 25GB to 7GB for new users. Existing users need to perform manual action to keep 25GB.

Microsoft SkyDrive is decreasing the storage available to users from 25GB to 7GB. Existing users however can keep the 25GB but manual action is required: http://ludwigkeck.wordpress.com/2012/04/23/get-your-free-25-gb-of-skydrive-storage/

Also keep in mind that Microsoft Skydrive will become more and more integrated with Windows 8 and that they have also released an application (like dropbox) that also works for previous Windows versions. For more information check:

UPDATE:

Google drive has also launched and also dropbox is making improvements to its service. Before deciding to use any service however, compare their terms of use: http://www.theverge.com/2012/4/24/2972228/cloud-storage-terms-of-service-comparison-avoid-google-drive

 
Leave a comment

Posted by on April 24, 2012 in Cloud, ICT, Microsoft, Public Cloud

 

Tags: , , ,

Windows 8 Consumer Preview first impressions

As most of the IT people already know, Windows 8 Consumer Preview has been released which can be used until January 15, 2013. More information and download links can be found here: http://preview.windows.com/

Even though there are a lot of changes as shown in this article, the main areas I’m interested in are:

  • Metro interface
  • Powershell 3.0
  • Hyper-V 3.0 on the client

As a side note, the Pinball FX2 game has been included, which is one of my favourite pinball games. The Sorcerer’s Lair Table will be free for all Windows 8 users and more pinball tables are expected in the future.

Besides the Windows 8 Consumer Preview, a beta for the Windows 8 Server has also been released, which I will cover at another time.

Metro interface

Since I don’t own a Windows Phone 7, the Metro interface is new to me. I have to say it did not take that much time getting used to, but I did find this video invaluable to getting started:
http://channel9.msdn.com/Blogs/Windows-Blog/Windows-8-Consumer-Preview-Demo

My first impression about the Metro interface is that it looks nice. I’m still in doubt about how useful it will be, but this all depends on the applications being created so it’s a bit early to tell.

Also as a long time Windows user I often find myself reverting to desktop mode. In desktop mode another thing to get used to, is that there is no start menu. By creating desktop shortcuts or  pinning documents to the taskbar this works fine, but it still feels strange.

Powershell 3.0

With Powershell 3.0 some of the major improvements include:

  • Much improved Integrated Script Editor (ISE)
  • More cmdlets (pre-defined commands)
  • Simplified use

For some more information about some of the new or improved feature you can also check:
http://www.computerperformance.co.uk/powershell/index_v3.htm
http://jdhitsolutions.com/blog/2012/02/powershell-3-0-easy-rider/

Hyper-V 3.0

Windows 8 will be the first client OS where you can install Hyper-V. This is great, because as a Microsoft administrator I want to test new operating systems and applications using a virtual testing environment for that. I could of course dual-boot my PC with both a client OS and a server OS, but this is inconvenient. I could also use VMware workstation or any other virtualization solutions, but this causes additional overhead since it is not a type 1 hypervisor. Also Microsoft provides pre-configured environments in the VHD format, which would require additional effort to get them to work correctly in other virtualization solutions.

One of the downsides of the new Hyper-V 3.0 however is that you need a 64-bit processor with Second Level Address Translation (SLAT). With Intel support for this is through a technology called Extended Page Tables (EPT) while with AMD it’s called Nested Page tables (NP). For intel it requires you to have an Intel Core i3, i5, i7 or newer. You can also check with coreinfo if your CPU is supported.

Since my current pc does not meet this requirement, I have not been able to check Hyper-V 3.0 yet. Due to a misstake by Dell however, I expect to be able to test it on my new laptop next week.

For more information regarding new and improved Hyper-V features, please check this article at WindowsITPro.com.

 
Leave a comment

Posted by on March 3, 2012 in Windows, Windows 8

 

Tags: , , ,

System Center 2012 Configuration Manager beta exam

Exam experience

System Center 2012 Configuration Manager exam:
70-243 Administering and Deploying System Center 2012 Configuration Manager

*Taken 23-02-2012*

Preparation materials

Configuration Manager

System Center 2012 Configuration Manager Survival Guide
MVP Raphael Blog

Nico Sienaert’s System Center Blog

Systemcenterblog.nl
MS Tech Blog
Windows-Noob.com step-by-step guides
Technet Virtual Labs
Configuration Manager TechCenter

Configuration Manager TechNet Library

System Center Configuration Manager 2012 Beta”How Do I?” Videos

System Center Configuration Manager 2012 Product Page

Microsoft Events regarding System Center Configuration Manager 2012
System Center Configuration Manager 2012 Forum
System Center Configuration Manager 2012 Blog
Technical Reference for Site Administration in Configuration Manager (ports, log files, accounts)

Cloud

Microsoft Private Cloud Evaluation Software
Cloud fundamentals video series
Private Cloud Jump Start
Virtualize Your Way to the Cloud with Hyper-V

TechNet Radio: Virtual Lab Insider: Building Your Cloud Infrastructure with Virtual Machine Manager 2012
TechNet Webcast: Hyper-V: The Base of a Private Cloud

New and improved in 2012

http://technet.microsoft.com/en-us/library/gg699359.aspx

Installation

  • During setup the supplied parameters are saved to an answer file in %TEMP%\ConfigMgrAutoSave.ini so you can re-use it.

Clients

  • To support the new 64-bit client, the location of the CCM folder for client-related files (such as the client cache and log files) has changed from %windir%\system32 to %windir%. If you reference the CCM folder for your own script files, update these references for the new folder location for Microsoft System Center 2012 Configuration Manager clients.
  • Client health rules in %windir%\CCM\ccmeval.xml on the client.
  • Client installation methods and their (dis)advantages
  • Ccmsetup.exe switches

Collections

  • Collections contain resources from all sites in the hierarchy.
  • You can no longer combine user resources and device resources in the same collection. Also important for migration preparation.
  • Use include rules to progressively increase the membership of a collection. You can include or exclude the contents of another collection from a specified collection.For by example phased deployments.
  • A collection is always a subset of its limiting collection.

Compliance and settings management

  • Previously called Desired Configuration Management (DCM)
  • A new built-in security role named Compliance Settings Manager
  • Alerts can be configured for exceeding thresholds (% of systems non compliant).
  • Device and user focus.
  • Compatible with managed mobile devices.
  • Detect and report conflicting compliance rules.
  • Not supported in 2012 anymore:
    • Uninterpreted configuration items (remove before migrating)
    • Settings groups
    • Regular expressions for settings
    • Using wildcards for registry settings
    • The string operators Matches and Do not Match

Asset Intelligence

  • You can now download the Microsoft Volume Licensing Service (MVLS) license statement from the Microsoft Volume Licensing Service Center and import the license statement from the Configuration Manager console.

Mobile devices

  • Enrollment now natively supported by using the new enrollment point and enrollment proxy point and a Microsoft enterprise certification authority.
  • Mobile device management responsibility can be moved from Exchange to configuration manager using the exchange server connector (supports Exchange 2010 and Exchange Online).
  • Requires PKI (was not the case with 2007).
  • Mobile device legacy clients can still be managed, but with limited functionality.

Endpoint protection

  • System Center 2012 Endpoint Protection is now integrated with SCCM2012
    • No seperate setup/dashboard. For the install just select the Endpoint Protection Point site system role. For the dashboard select the System Center 2012 Endpoint Protection Status node in the Monitoring workspace.
    • No package and program used to install endpoint protection client (install using SCCM2012 client settings or manage existing cients).
    • Endpoint Protection Manager role provides admin with minimum permission to manage Endpoint Protection.
    • New integrated reports (including user centric).
    • Auto update using automatic update deployment rules.
    • Configurable SCCM2012 alerts and subscriptions.

Software updates

  • Uses Software Distribution Point site role (WSUS)
  • Automatic approval and deployment.
  • Improved search with expanded criteria.
  • Greater user control for scheduling installation.
  • Software update groups.
  • Software update files are stored in the content library (single instance store for content files).
  • Software deployment templates (by example template with deadline 0 days and allow restarts outside of maintenance windows for highly critical updates)
  • Internet-based clients try to retrieve update files from the Internet first. If impossible will fallback to distribution point.
  • Enhancements to software updates monitoring:
    • Reports.
    • Key software updates compliance+deployment views.
    • Detailed state messages for deployments+assets.
    • Software updates error codes with additional information to help identify issues.
    • Status for software updates synchronization.
    • Alerts for key software updates issues.

Application management

Applications are new in SCCM 2012 and have the following characteristics:

  • Contain files + information to deploy software package to device.
  • Multiple deployment types possible:
    • Local install
    • Virtual application package
    • Mobile package
    • Session virtualization (RDS/XenApp)
  • Requirement rules define conditions that specify how applications are deployed. By example:
    • Hardware requirements
    • Primary device of user ?
  • Global conditions are similar to requirement rules, but can be reused with any deployment type.
  • User device affinity allows you to associate a user with specified devices, allowing you to deploy software to a user rather than a device. You could deploy an application so that it only installs on the primary device of the user. On non primary devices, you could deploy a virtual application that is removed when the user logs out.
  • Deployments are used to distribute applications. A deployment can have an action which specifies whether to (un)install the application and a purpose whether the application must be installed or whether the user can choose to install it.
  • Detection methods (script/product information) can be used to determine if a deployment type has already been installed.
  • Status can be monitored directly in the configuration manager console (as opposed to only using reports).
  • Packages and programs from 2007 are supported and can use some of the new deployment and monitoring features.
  • Task sequences can be deployed on the internet like by example scripts. Operating system deployment over the internet is still not supported.
  • Software Center is a new client interface that allows users to request and install applications, control some client functionality, and to access the Application Catalog, which contains details about all available applications.
  • How-to for applications

Operating System Deployment

  • Windows Updates can be applied offline directly to the WIM.
  • Task Sequence Media Wizard includes steps to add prestart command files (formerly pre-execution hooks) to prestaged media, bootable media, and stand-alone media.
  • Task Sequence Media Wizard option to suppress wizard. Unattended install.
  • The same task sequence media can be used to deploy operating systems to computers anywhere in the hierarchy.
  • Capture/Restore User State task sequence action supports new features from USMT 4.
  • Use Install Application task sequence action to deploy applications from the Software Library when you deploy OS.
  • Define user device affinity for a device during OS deployment.
  • PXE service point configuration and functionality moved to the distribution point.

Content Management

  • Distribution point role
    • Only one role (opposed to standard/branch role 2007).
    • Can be installed on workstations+servers.
  • Content library
    • Where all content files are stored for software updates, applications, operating system deployment, etc.
    • Located on the site server and each distribution point.
    • Single instance store (no duplicate files as in 2007).
  • Content storage
    • Configurable drive (priority). Higher priority has preference until drive is below free space threshold (in 2007 the drive with most free space was used).
  • Prestaging content
    • Ensuring content is available even before it has been specifically requested.
    • Can be used for all package types.
    • Prestaged content is compressed and contains the files and associated metadata.
    • Combined with bandwidth throttling and scheduling this gives you more control over bandwidth usage.
    • The distribution point can be configured for prestaging.
    • When you distribute content you can choose to:
      • Always prestage the content on the distribution point.
      • Prestage the initial content for the package but use the normal content distribution process for updates.
      • Always use the normal content distribution process.
    • During the import process, Configuration Manager detects version conflicts and will prevent the content for an older version of the package from being prestaged.
  • Bandwidth throttling and scheduling between the site server and the distribution point.
  • PXE service point
    • Integrated in distribution point role. No seperate role.
    • DP certificate is used for PXE as well.
    • No PXE share for boot images. Instead an attribute of the boot image is used and the image is automatically deployed to the PXE store.
    • Multicast options integrated with DP.
  • BranchCache integration with more granular control. Configure on deployment type for applications and on deployment for package.
  • Distribution point groups
    • Logical grouping of content distribution points.
    • Eases administration (assign content to group).
  • Content validation
    • Check integrity manually or scheduled.
    • View status reports in the monitoring workspace.
  • Management of content files
    • Manage content from the properties of distribution points, distribution point groups, and package types (for example, application, deployment package, driver package, etc).
    • From the distribution point and its properties, see all package types assigned for distribution.
    • From the package properties, see all distribution points and distribution point groups in which the package has been distributed. You can redistribute, validate, or remove the content from the properties for the object.
  • Content monitoring
    • Reporting services point is the only site system role that System Center 2012 Configuration Manager uses for reporting.
    • SQL 2008 Server Reporting Services (SRS) support and new added functionality.
    • SQL 2008 SRS Report Builder 2.0 integration.
    • SQL 2008 SRS report subscriptions (schedule and mail or put on share).
    • Localized reporting depending on installation locale of:
      • Configuration Manager Console
      • SQL 2008 SRS

Alerts

  • New in SCCM 2012
  • Provides near real-time awareness of current site operations and conditions in the configuration manager console.
  • Alerts are stat-based and will automatically update.

Database Replication

  • Database replication is new in SCCM 2012.
  • Monitor the status using Database Replication node in Monitoring workspace of Configuration Manager console.
  • Uses SSB (SQL Service Broker) on port 4022
 

Tags: , , , , , , , , , ,

Office 365 beta exams experience

Exam experience

Today I took the Office 365 beta exams:
70-321 Deploying Office 365
70-323 Administering Office 365

In my opinion the 70-323 was pretty tough, while the 70-321 was a lot easier. I expected it to be the other way around though. Now unfortunately I have to wait for the results (normally within 8 weeks).

Quick exam reminders I studied before the exams

  1. Deployment phase
    1. Office 365 Deployment Phases
    2. Office 365 Deployment Schedule
  2. Plan phase
    1. Key activities
    2. Office 365 Enterprise License Plans
    3. Office 365 Administration roles
    4. Exchange Hybrid Solution Infrastructure overview picture
    5. High Level Tasks For Exchange Hybrid Deployment
  3. Prepare phase
    1. Key activities
    2. Update schema for Exchange 2010 :
      cd c:\exchangeserver2010sp1 and then setup /preparead
    3. Office 365 ports, ips and urls
    4. Exchange Hybrid Deployment Domain and Host Names Worksheet
    5. Configure SSO with ADFS:
      Connect-MsolService –Credential $cred
      Set-MsolAdfscontext -Computer <AD FS 2.0 primary server>
      New-MsolFederatedDomain –DomainName <domain>
    6. Configure dirsync (separate server and when less than
      50.000 objects SQL 2008 Express will do).
    7. Mail migration types and explanation E-mail migration overview (virtual labs)
  4. Migrate phase
    1. Key activities
    2. Post-deployment services testing plan

Resources used as preparation

 

Tags: , , , , , , , , , , ,

 
Follow

Get every new post delivered to your Inbox.