Posts Tagged ‘Windows 2008 R2’

Device Manager is running in read-only mode

Written by M.Pol on . Posted in Microsoft, VMware

Today I was creating a template for my VMware environment, when I was trying to change the graphical interface card I was running into some problems. This is the message the Device Manager is giving me.

The result is that I cannot change any drivers or devices.

The solution is very simple but not obvious. My computer name is longer than 15 characters. This is a problem for NetBIOS computers. It turns out this is also a problem for the device manager. So I changed my computer name to a name with less than 15 characters, now everything works normal again.

Reset Domain Administrator Password

Written by M.Pol on . Posted in Microsoft

A Client of our company had a problem, they got in an argument with their current IT Management company. Eventually the IT Management company wouldn’t give up the administrator account password of the complete domain. So this client was locked out of his own network. We were asked if there was a way to reset this password. So I started looking on the internet for some solutions.

The first one I tried in my own lab was the one that Daniel Petri describes in het Blog post at: http://www.petri.co.il/reset_domain_admin_password_in_windows_server_2003_ad.htm

There were some requirements for this trick.

  • Local access to the domain controller (DC).
  • The Local Administrator password.
  • Two tools provided by Microsoft in their Resource Kit: SRVANY and INSTSRV. Download them from HERE (24kb).

The first one was no problem, but the second one in my case was a problem, we didn’t no the local administrator password.

So this is how I did it, first of all download the DART tools (Diagnostics and Recovery Toolset) from the Microsoft website, this is available for MDOP License owners. See http://www.microsoft.com/windows/enterprise/products/mdop/dart.aspx

There are other ways to get your hands on this tool, go to the Technet site and get a Technet Subscription. And if you don’t have access to both sources, go search Google.

I restarted the domain domain controller, and boot into the DART tool. Go to the Locksmith tool, and reset the password of the Administator account. Reboot the server, in Active Directory Recovery mode. This is important because now the Local accounts are available for logon. The local accounts are disabled on a Domain Controller, this is by design. In recovery mode logon with your new local Administrator password. Now do the trick that Daniel Petri describes in his post.

This is how it works globally.

Step 1

Restart Windows 2003 in Directory Service Restore Mode.

Note: At startup, press F8 and choose Directory Service Restore Mode. It disables Active Directory. When the login screen appears, log on as Local Administrator. You now have full access to the computer resources, but you cannot make any changes to Active Directory.

clip_image001

Step 2

You are now going to install SRVANY. This utility can virtually run any programs as a service. The interesting point is that the program will have SYSTEM privileges (LSA) (as it inherits the SRVANY security descriptor), i.e. it will have full access on the system. That is more than enough to reset a Domain Admin password. You will configure SRVANY to start the command prompt (which will run the ‘net user’ command).

Copy SRVANY and INSTSRV to a temporary folder, mine is called D:\temp. Copy cmd.exe to this folder too (cmd.exe is the command prompt, usually located at %WINDIR%\System32).

Start a command prompt, point to d:\temp (or whatever you call it), and type:

instsrv PassRecovery "d:\temp\srvany.exe"

(change the path to suit your own).

It is now time to configure SRVANY.

Start Regedit, and navigate to

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PassRecovery

Create a new subkey called Parameters and add two new values:

name: Application

type: REG_SZ (string)

value: d:\temp\cmd.exe

name: AppParameters

type: REG_SZ (string)

value: /k net user administrator 123456 /domain

Replace 123456 with the password you want. Keep in my mind that the default domain policy require complex passwords (including digits, respecting a minimal length etc) so unless you’ve changed the default domain policy use a complex password such as P@ssw0rd

Now open the Services applet (Control Panel\Administrative Tools\Services) and open the PassRecovery property tab. Check the starting mode is set to Automatic.

clip_image002

Go to the Log On tab and enable the option Allow service to interact with the desktop.

Restart Windows normally, SRVANY will run the NET USER command and reset the domain admin password.

Step 3

Log on with the Administrator’s account and the password you’ve set in step #2.

Use this command prompt to uninstall SRVANY (do not forget to do it!) by typing:

net stop PassRecovery

sc delete PassRecovery

Now delete d:\temp and change the admin password if you fancy.

Done!

Microsoft Test Lab Guides

Written by M.Pol on . Posted in Microsoft

Recently Microsoft released a lot of Lab Guides for different Microsoft products to test. See http://social.technet.microsoft.com/wiki/contents/articles/test-lab-guides.aspx

Test Lab Guides

Test lab guides (TLGs) allow you to get valuable hands-on experience with new products and technologies using a pre-defined and tested methodology that results in a working configuration. When you use a TLG to create a test lab, instructions define what servers to create, how to configure the operating systems and system services, and how to install and configure any additional products or technologies. A TLG experience enables you to see all of the components and the configuration steps on both the front-end and back-end that are required for a product or technology or for a multi-product or technology solution.

A challenge in creating useful TLGs is to enable their reusability and extensibility. Because creating a test lab can represent a significant investment of time and resources, your ability to reuse and extend the work required to create test labs is important. An ideal test lab environment would enable you to create a basic lab configuration, save that configuration, and then build out multiple test lab scenarios in the future by starting with the base configuration.

For a test lab based on physical computers, you can image the drives for future test labs. For a test lab based on virtual machines, you can create snapshots for future test labs. This allows you to easily return to a desired configuration for further learning and experimentation.

The types of TLG documents are the following:

  • Base configuration TLG
  • Modular TLGs
  • TLG extensions
  • Troubleshooting TLGs
  • Test lab troubleshooting scenarios
  • TLG portal pages

Base Configuration TLG

The Base Configuration TLG allows you to create the base configuration test lab, upon which you can build test labs based on other TLGs from Microsoft, TLG extensions in the TechNet Wiki, or a test lab of your own design that can include Microsoft or non-Microsoft products.

The base configuration TLG is just the beginning of the test lab experience. Other TLGs or TLG extensions in the TechNet Wiki focus on Microsoft products or platform technologies, but all of them use the Base Configuration TLG as a starting point.

After configuring the computers of the base configuration test lab, make sure that you perform a disk image on each computer if you are using physical computers, or perform virtual machine snapshots if you are using virtual machines.

Modular TLGs

A modular TLG describes how to set up and demonstrate a technology, product, or solution for either the Base Configuration test lab or a test lab based on another modular TLG.

The following modular TLGs are available:

To create your own modular TLG in the TechNet Wiki, see the Wiki: Modular Test Lab Guide Template.

TLG Extensions

A TLG extension article, published in the TechNet Wiki, describes how to configure additional functionality or advanced or uncommon configurations based on a working test lab. A TLG extension extends a modular TLG.

The TLG extension article includes instructions to configure and test the additional functionality, and then manually restore the test lab to its original state. A TLG extension article also includes virtualization advice so that you can create snapshots to store the modified test lab configuration and easily restore the original working test lab configuration.

Examples of TLG extensions are the following:

To create your own TLG extension, see Wiki: Test Lab Extension Template.

Troubleshooting TLGs

A troubleshooting TLG describes the troubleshooting tools and how they appear in a working test lab for a technology, product, or multi-technology and product solution. The working test lab is typically based on a modular TLG.

A troubleshooting TLG also takes you through a set of troubleshooting scenarios. Each troubleshooting scenario steps you through the following:

  • Breaking the configuration of the test lab in a specific way
  • Demonstrating the effect on the technology or product functionality
  • Performing root cause analysis of the problem using the troubleshooting tools and recommended troubleshooting techniques
  • Correcting the problem

The following troubleshooting TLGs are available:

To create your own troubleshooting TLG in the TechNet Wiki, see the Wiki: Troubleshooting Test Lab Guide Template.

Test Lab Troubleshooting Scenarios

A test lab troubleshooting scenario, published in the TechNet Wiki, provides an additional scenario to demonstrate the results of a misconfiguration or other type of common problem and guide the reader through the root cause determination and correction. Test lab troubleshooting scenarios extend a troubleshooting TLG.

For an example of a test lab troubleshooting scenario, click here.

To create your own test lab troubleshooting scenario, see Wiki: Test Lab Troubleshooting Scenario Template.

TLG Portal Pages

A TLG portal page is a TechNet Wiki article that provides links to all of the resources for a specific technology or product.

The following TLG portal pages are available:

Additional Resources

For the latest information about TLGs, see the Microsoft TLG blog.

Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2

Written by M.Pol on . Posted in Microsoft

For a project I was looking for a document about migrating from Windows 2003 Small Business to Windows 2008 R2 and Exchange 2010. I’ve found a great article written by demazter, this article describes every step. Original link: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html

This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010.

For this migration to work you will need the following software:

  • Windows Small Business Server 2003 (SBS 2003)
  • Windows 2008 Server or Windows 2008 R2 Server
  • Exchange Server 2010

Steps required:

  • 1.   Health Checks on Small Business Server 2003
  • 2.   Join new Windows 2008 Server to the domain as a member server
  • 3.   Prepare Active Directory for Windows 2008 R2 Server
  • 4.   Make Windows 2008 R2 Server a Domain Controller of the Existing Small Business Server 2003 Domain
  • 5.   Transfer DHCP Service
  • 6.   Install Exchange 2010
  • 7.   Installing Exchange 2010 SSL Certificate
  • 8.   Migrate Exchange Data
  • 9.   Migrate SharePoint Services
  • 10.  Migrate shared user data
  • 11. Uninstall Exchange 2003 from Small Business Server 2003
  • 12. Transfer all 5 FSMO roles to Windows 2008 Domain Controller
  • 13. DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network

It’s important that the steps are followed in order as different stages make different changes to the way in which your server operates.  For example you MUST make the 2008 server a domain controller before you install Exchange.

Prepare and Service Windows Images Using the New DISM Tool

Written by M.Pol on . Posted in Microsoft

Deployment Image Servicing and Management (DISM.exe) is a new command line tool that you can use to service a Windows image or prepare a Windows PE image. The DISM tool replaces the Package Manager (pkgmgr.exe), PEimg, and Intlcfg tools used with Windows Vista. DISM consolidates the functionality found in those three tools, as well as delivers new functionality to improve the experience of offline servicing.

DISM can be used to service Windows Vista with Service Pack 1 (SP1) and Windows Server 2008. When used with Windows 7 and Windows Server 2008 R2, you get the added functionality.
You can use DISM to:
  • Add, remove, and enumerate packages and drivers.
  • Enable or disable Windows features.
  • Apply changes based on the offline servicing section of an unattend.xml answer file.
  • Configure international settings.
  • Upgrade a Windows image to a different edition.
  • Prepare a Windows PE image.
  • Take advantage of better logging.
  • Service down-level operating systems like Windows Vista with SP1 and Windows Server 2008.
  • Service all platforms (32-bit, 64-bit, and Itanium).
  • Service a 32-bit image from a 64-bit host and service a 64-bit image from a 32-bit host.
  • Make use of old Package Manager scripts.

Command-Line Options

To service a Windows image offline, it must be applied or mounted. WIM images can be mounted using the Windows Image (WIM) commands within DISM, or applied and recaptured using ImageX.
You can also use commands to list the indexes or verify the architecture for the image you are mounting. After you update the image, you must unmount it and either commit or discard the changes you have made.
The base syntax for nearly all DISM commands is the same. After you have mounted your Windows image, you can specify any DISM options, the servicing command that will update your image, and the location of the mounted image. You can use only one servicing command per command line. If you are servicing a running computer, you can use the /online option instead of specifying the location of the mounted Windows Image.
The base syntax for DISM is:
DISM.exe {/image:<path_to_image> | /online} [dism_options] {servicing_command} [<servicing_argument>]
Movie : Technet

HP Sizer for Microsoft Hyper-V 2008 R2

Written by M.Pol on . Posted in HP, Microsoft

HP released an Sizer tool for Microsoft Hyper-V 2008 R2. Source : http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/microsoft-hyper-v2008.html

The HP Sizer for Microsoft Hyper-V 2008 R2 is an automated, downloadable tool that provides quick and helpful sizing guidance for “best-fit” HP server and storage configurations running in a Hyper-V R2 environment. The tool is intended to assist with the planning of a Hyper-V R2 virtual server deployment project. It enables the user to quickly compare different solution configurations and produces a customizable server and storage solution complete with a detail Bill of Materials (BOM) that includes part numbers and prices.

The HP Sizer for Microsoft Hyper-V 2008 R2 allows users to create new solutions, open already existing solutions, or use other types of performance data collecting tools, such as the Microsoft Assessment and Planning tool (MAP), to build rich Hyper-V R2 configurations based on HP server and storage technology. The tool allows rapid comparison of Hyper-V R2 characterizations using various HP server and storage choices.

Hyper-V How To: Plan Performance

Written by M.Pol on . Posted in Microsoft

Good read from Microsoft. Source : http://blogs.technet.com/tonyso/archive/2009/11/30/hyper-v-how-to-plan-performance.aspx

Customers often ask “Given a hardware load-out X, how many Ys can I get/run/host?”

The frustrating answer always starts with “…it depends…”. We caveat this way not because we want to frustrate, but because it is true. Many teams will go on to say “We have tested the following in our labs and gotten the displayed results…”

1 X = thingy

2 X = more thingies

3X = many more thingies

While accurate, not super-helpful.

The truth is that to do good perf planning for Hyper-V you have to run some tests.

Run them using your actual production load (converted to Virtual Machines) in a test environment.

TIP: you can download the free VHD version of SCVMM, then run it as a VM to convert your production machines to “test” virtual machines.

Then play with your assumptions and tweak things higher and lower and to your design tolerance and actually observe how perf goes.

Add an overhead/forgot-to-test percentage, done.

Windows 7 and Windows Server 2008 R2 – HOT ISSUES LIST

Written by M.Pol on . Posted in Microsoft

A series Windows 7 and Windows Server 2008 R2 issues have been reported to Microsoft customer support. From these issues, we figured out several hot issues and authored Knowledge base articles to explain the solutions.

To identify and troubleshoot these issues, you can find more information from the KB articles:

  • 975787 Adjust User Account Control settings in Windows 7
  • 976832 Error message when you insert a smart card in a reader on a Windows 7-based or Windows Server 2008 R2-based computer: “Device driver software was not successfully installed”
  • 975784 Enable the Quick Launch bar in Windows 7
  • 975785 Customize the notification area in Windows 7
  • 975786 Customize the notification area in Windows 7
  • 975788 Turn off the secure desktop in Windows 7
  • 976034 Get a detailed Power Efficiency Diagnostics Report for your computer in Windows 7
  • 976170 Troubleshoot Aero problems in Windows 7
  • 976877 Troubleshoot Aero problems in Windows 7
  • 976736 How to install Windows PowerShell on a computer that is running Windows Server 2008 R2 Core
  • 2006291 Error message When You Bring up the Server Manager Console and click on Add / View Roles: “0x800B0100″
  • 977510 Authentication fails when an external client tries to log on by using a read-only domain controller in a perimeter network

Source: http://blogs.technet.com/ferris/default.aspx

Create an All-in-one x86+x64 Win7/Vista/Server 2008/R2 USB stick

Written by M.Pol on . Posted in Microsoft

One of the great things about the Vista and post-Vista operating systems is that the installer subsystem allows you a great deal of flexibility when it comes to installing multiple operating systems. It is fairly easy to put together a single installation DVD or USB stick that will allow you to install Vista, Windows 7, Server 2008 and Server 2008 R2 – in a variety of x86 and x64 flavors.

A couple of things to note about this guide:

  • I do not use Vista — I have never really used Vista and now with Windows 7 out there really is no reason to; however the steps here will work just fine with Vista installation sources
  • I have only tested this using a USB stick and will only cover that method here – it’s much more flexible (and faster) for installation than using DVD — but DVDs should work just fine: you can find plenty of tutorials on the web that will tell you how to use oscdimg.exe to take the files we create here and turn them into a burnable ISO

WHAT YOU WILL NEED:

  • USB stick, at least 4 GB (perhaps larger depending on how many OSes you plan to integrate, I use a 16 GB) that has been properly formatted using Steps 1 and 2 here
  • ISOs or DVDs of the operating systems that you plan to integrate
  • imagex.exe (can be found for download on the web, or you can download the full 1.7 GB WAIK here)
  • computer running Vista or newer operating system (XP should work but I have not tested it)