Your company's ad could live here and reach over 50,000 people a month!

Share This Post

Installing the new MDT Web FrontEnd Beta

As written in my last blog post, the first Beta of the MDT Web FrontEnd Version 2 has just been published. If you plan to test this version (what I really would appreciate), keep in mind, that it’s a Beta version. It shouldn’t be used in production. It’s provided “AS IS”, you know the game.

The Beta has been tested on Windows Server 2008 R2 and Windows Server 2008 64 and 32 Bit. The only real requirement is the .Net Framework 4.

Just follow these few steps, to get the Beta running:

Download the Beta Version from CodePlex

– Make sure that you unblock the file

image

– Extract the content of the zip file to a folder of your choice. I would recommend the Web Root of your web server (e.g. C:\Inetpub\wwwroot). If necessary, rename the folder to something more appropriate.

– Open IIS Manager, I suggest to create a new application pool for the FrontEnd. Be sure to configure .Net Framework 4 for it.

imageimage

– Make sure you set an appropriate user account for the application pool. It should have enough permission to access the MDT Database (or enough permission to create it, if it doesn’t exist already), connect to Active Directory to query for AD Sites, connect to ConfigMgr and also query some view in the ConfigMgr Database. You can also configure different accounts to be used later in the FrontEnd.

SNAGHTML3783d01

Now expand the web root, right-click the folder and convert it to an application. If you extracted it to a different location, create a new application and point to this folder

image

– Make sure that Windows authentication is enabled, and anonymous Authentication is disabled.SNAGHTML393dc7b

Now you should be able to open the MDT Web FrontEnd and see the welcome page.

image

If you get an error message stating something like “The Web server is configured to not list the contents of this directory or something similar. It’s most likely, that the .Net Framework 4 hasn’t correctly registered with IIS.

To register it again, just run the following command from an elevated prompt on a 64 Bit Windows:

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir

Or this command on a 32 Bit version:

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir

If you can’t find this path, check the %windir%\Microsoft.NET\Framework64 or %windir%\Microsoft.NET\Framework\ folder, as you might have a slightly different Framework version.

After that, you should be able to open the web page.

Next step now should be to configure access to the MDT Database. For this click on “Configuration – MDT related settings”

Type in the name of your Database server and click on “Save Changes”. The page should now reload and present you with a list of databases to choose from. If not, you might have a typo in the name or the account simply doesn’t have permission to access the Database server. Check the “Status” for more information.

Now choose the appropriate Database (or type in a Name for a new database) and click on “Evaluate Database”. It will verify the version of the database. Now click on “Upgrade Database”, to run the database scripts, that will add all the Frontend extensions to an existing MDT Database, or even create a completely new database.

SNAGHTML39f4a5b

Make sure you check the “Enable enhanced features” option and Save the changes!

Next step is to get the Active Directory Sites. Click on “Configuration – Active Directory Configuration”. Click on “Get AD Sites” to start the AD Site Discovery. Optionally specify the Domain to query, and the credentials to be used for this. The discovery will fill the grid further down the page. Use this to e.g. edit the name of the Location or mark some of them to be hidden from the frontend, when selecting AD sites.

image

Last step is to discover your ConfigMgr environment, if available. Click on “Configuration – SCCM Configuration”. Specify the name of your central ConfigMgr server, optionally define username and password, and click on “Get Primaries” to discover the ConfigMgr environment. It will now connect to each available primary and gather some information like SiteCode, Providerversion and configured database. You can edit this data later in the grid shown below:

image

That’s it. Now the FrontEnd is ready for use.

As mentioned already, it’s Beta code, there is still some stuff to do. So please help by testing it, filing problems and making suggestions on how to make it even better.

Download the current Beta now from CodePlex.

And please make use of the Issue Tracker and the Discussions Forum.

Share This Post

Leave a Reply