Tag Archives: .net

How To Install Exchange 2016 (Greenfield Site) – Part 2

Posted on by
2

KB ID 0001302

Problem

Back in Part-One, we looked at all the things to consider before you start to install Exchange 2016. Now we will start installing software, and getting to a point where we can configure Exchange 2016 and carry out some post deployment.

Solution

Your forest functional level needs to be at ‘Windows Server 2008’ before you can install Exchange 2016.

The server you intend to deploy Exchange on, needs to be a domain member server.

To save you any hassle, make sure your intended server is fully updated.

The server needs .Net installing, the versions, (at time of writing ) are;

  • Exchange 2016 CU3 Req.Net 4.5.2 (or greater).
  • Exchange 2016 CU5 Req.Net 4.6.2 (or greater).
  • Exchange 2016 CU6 Req.Net 4.7.2 (or greater).

Exchange 2016 Roles/Features Windows Server 2016

As with previous versions of Exchange there’s a long list of roles and features that needed to be added, open an administrative PowerShell Window and run the following;

[box]

Install-WindowsFeature NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS, Server-Media-Foundation

[/box]

Exchange 2016 Roles/Features Windows Server 2012 (2012 R2)

As with previous versions of Exchange there’s a long list of roles and features that needed to be added, open an administrative PowerShell Window and run the following;

[box]

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS

[/box]

You will also need to install the ‘Unified Communications Managed API 4.0 Runtime‘ software. Note: Not required if you are only installing the management tools.

Windows Server 2016 Only: You should already have update KB3206632 as we updated the server above, if you skipped that step you need to pre install that update, so update now!

Installing Exchange 2016

If you downloaded the Exchange media as a .iso file mount it and let it autoplay. If you extracted the software run Setup.exe. The first thing it will do is look to see if it has any updates.

Files will get copied over > Next > You will be presented with an introduction > Next.

Accept the EULA > Next > I usually just accept the recommended settings > Next.

Select either Mailbox server, Edge Transport server, or just the management tools > Next > Select the location that you want to install Exchange to > Next.

Note: Although in the example below, I’m using the ‘C:’ drive, for production I would always install Exchange onto a separate volume to the OS.

I usually accept the default organisation name of ‘First Organisation’ you can change it if you with, but choose wisely because you can’t change it once installed > Next > Unless you have a specific requirement to disable the built in malware protection, leave it enabled > Next.

Exchange now does a quick check to make sure it’s happy to progress, you will always get a couple of warnings, if it complains about anything else rectify it and click ‘recheck’, once you are happy click Next.

Setup progress takes ages! Seriously go to lunch at this point > Next > Once completed Ive ticked the box to open the Exchange Admin Center, but nearly every time I’ve done this it fails. Your best bet is to reboot the server, go and have a coffee then come back and open a browser window and navigate to https://{server-FQDN}/ecp 

In Part 3, we will look at post install tasks.

Related Articles, References, Credits, or External Links

How To Install Exchange 2016 (Greenfield Site) – Part 1

Installing vSphere VI Client on Server 2012 Fails – Error 28173

Posted on by
Reply

KB ID 0001139

Problem

If you attempt to install the VI client, (in this case on a 2012 R2 Datacenter Server), you may see this error;

Error 28173. Setup failed to enable Microsoft .NET Framework 3.5 Refer to Microsoft KB article 2734782 and 3002547 which may help you resolve the .NET failure. You will need to enable this feature in Windows Server Manager before installing vSphere Client.

Solution

I’ve had problems with .NET on server 2012 before, so let’s cut out the middle man and install it directly from the install media. Pop in the server 2012 DVD. Then execute the following command in PowerShell, (change drive letter accordingly);

[box]

Install-WindowsFeature -Name NET-Framework-Core -Source D:\sources\sxs

[/box]

Then make sure you reboot the server and try again.

Related Articles, References, Credits, or External Links

NA

Event ID 1023

Posted on by

KB ID 0000176 Dtd 03/02/10

Problem

Event ID 1023

Source : .NET Runtime
Description : .net Runtime version 2.0.50727.3603 – Fatal Execution Error (7a09795e) (80131506).

Symtoms:

1. As above. seen on .net version 2.0.50727.3603 Note: you version number may be different.

2. Backup Exec Server Service may be stuck / hung in the “starting” state.

3. .net 2 cannot be removed or service packed.

Solution

1. Download this, then apply the relevant 32 or 64 bit hot fix.

2. Reboot the affected machine.

Related Articles, References, Credits, or External Links

NA

Microsoft SQL – ‘Error While Enabling Windows Feature : NetFx3’

Posted on by

KB ID 0000958 

Problem

I was installing SQL Server 2012 and suddenly this popped up;

The following error has occurred:
Error while enabling Windows feature: NetFx3, Error Code: -2146498298, Please try enabling
Windows feature: NetFx3 from Windows management tools and then run setup again. For more
information on how to enable Windows features, see http://go.microsoft.com/fwlink/?linkid=227143

Solution

I’ve been bitten by .Net on Server 2012 before. Leave this error on the screen, and the install in the background, and pop in the Sever 2012 Installation DVD, then run the following command;

[box]

Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:sourcessxs /LimitAccess

Where D: is the DVD Drive Letter

[/box]

Put the the SQL Install media back in the drive if you removed it, (I was installing from a mounted .ISO file), click OK on the error message and SQL should continue to install.

Related Articles, References, Credits, or External Links

NA

Install SCCM 2007 on Windows Server 2008 R2 – Step by Step

Posted on by

KB ID 0000297

Problem

I had to work out how to do this for a client, and as is my modus operandi, I’ll try and save you some of the pain I endured,

Products Used

System Center Configuration Manager 2007 SP2 Windows Server 2008 R2 SQL 2008 R2 (At time of writing neither officially supported or not supported on SCCM)

Note: I was originally going to use SQL 2005 – hence the reason the SQL servers name is SCCM-SQL2005, however I bit the bullet and used SQL 2008 R2 instead.

Solution

Step 1: SCCM Domain pre install work.

1. Create two groups in Active Directory.

a. sccm administrator group SCCM-ADMIN b. sql administrator group SQL-ADMIN

2. Add both groups to the Domain Admin’s group.

3. Create two new users: sccmadmin and sqladmin.

4. Add sccmadmin to SCCM-ADMIN group and add sqladmin to SQL-ADMIN group.

Step 2: SCCM Pre requisites

1. Add the IIS (Web Server Role).

2. Add the following IIS Role Services:

a. HTTP redirection. b. ASP.Net

c. Windows Authentication. d. IIS6 Metabase compatibility. e. IIS6 WMI compatibility.

3. Add the following “server Features”:

a. Background Intelligent Transfer Service. b. Remote Differential Compression.

4. If you are NOT running Windows Server 2008 R2 Download and install WebDav (already included in Windows Server 2008 R2). If you are running R2 skip to the next step.

5. Server Manager > Roles > Web Server (IIS) > Add Role Services > WebDAV Publishing > Next > Close.

6. To enable WebDav > Start > Administrative Tools > Internet Information Services (IIS) Manager > Expand {server name} > Sites > Default Web Site > WebDav Authoring Rules.

7. Select Enable WebDav (On the right hand side).

8. Select add authoring Rule > All Content > All Users > Permissions > Read > OK.

9. Select the rule you have just created > WebDav Settings.

10. Change “Allow Anonymous Properties Queries” to True > Change “Allow Custom Properties” to False > Change “Allow Property Query with Infinite Depth” to True > Change “Allow hidden files to be listed” to True > Apply.

11. WSUS needs to installed on the SCCM server – Note Server 2008 R2 needs (WSUS Server Update Services 3.0 SP2). If you try and install SP 1 you will see this error.

12. From the WSUS installation choose “Full server installation” > DO NOT accept the default “Use the existing IIS Default Web site” > Use “”Create a Windows Server Update Services 3.0 SP2 Web site” (Note: this will use port TCP 8530 by default).

Step 3: SCCM Install SQL Server.

1. From the SQL install media run setup.exe > Installation > “New Installation or add features to an existing Installation” > OK.

2. Enter product Key if applicable > Next > “I accept…” > Next > Install > Next > Next.

3. Tick Database Engine Services > Tick Management Tools (Basic and Complete) > Next.

4. Next > Accept the defaults > Next > Next.

5. On the Server configuration Page > Select “Use the same account for all SQL Server services > Select the User you created originally (sqladmin) > Set the SQL Server Agent and SQL Server Database Engine Startup type to “Automatic” > Next.

6. Accept “Windows Authentication” > Add in your SCCM-ADMIN group and SQL-ADMIN group > Next > Next > Next > Install.

7. When it’s completed click close.

Step 4: Prepare Active Directory for SCCM

1. Extend the schema > From the install media > SMSSETUP > BIN > 1386 > extadsch.exe

2. Check the above was successful by opening the c:extADsch.txt file it should say “”successfully extended the Active Directory Schema”.

3. We now need to create some active directory objects go to a domain controller > Start > Administrative tools > ADSI Edit > Action > connect to > leave everything on its defaults > OK.

4. Expand the Default naming context > Expand your domain name > Right click “system” > New > Object > Container > Next.

5. Call it “System Management” > Next > Finish > Close ADSI Edit.

6. Still on the domain controller > Start > dsa.msc {enter} > View > Advanced.

7. Expand “system” > Locate the container you created “System Management” > right click it and select properties > Security Tab > Add > Object Types > Tick Computers > OK.

8. Click Advanced > Find Now > Locate and add the SCCM-ADMIN group you created earlier > Also add the SCCM Server itself > OK.

9. Grant allow “Full Control” to both the SCCM admin group and the SCCMserver.

10. Now click advanced > Select the SCCM-ADMIN group > Edit.

11. Change the “Apply to” section from “This object only” to “This object and all descendant objects” > OK > Apply > OK.

12. Repeat the above for the SCCM-Server object.

Step 5: Install SCCM

1. Log on as the sccadmin user.

2. From within the SCCM setup media run splash.hta > Run the Pre requisite checker > Enter the SQL Server name > SCCM server name and the FQDN of the SCCM server > OK.

3. Note If you cannot talk to the SQL server then check that the Windows firewall is not blocking you (on the SQL server Start > run > firewall.cpl > Turn it off).

4. All being well it should say “All required pre requisite tests have completed successfully” > OK.

5. Re-run Splash.hta > This time choose > Install configuration Manager 2007 SP2 > Next > “Install Configuration Manager site Server > Next.

6. Tick “I accept these License terms > Next > Custom Install > Next > Primary Site > Next > Next > enter unlock code is applicable > Next > Accept/change the install directory > Next > Enter a Site code and friendly name > Next.

DO NOT ever try and change this code and don’t forget it!!

7. Change the Site mode to “Configuration Manager Mixed Mode” (Native mode requires certificate services and considerably more work). > Next.

8. Accept the defaults (everything except NAP) > Next.

9. Enter your SQL server name > Next > Next > Next > Next > Next.

10. Select a location to install the updates to > Next.

11. Updates will download this may take some time > when finished it should say it was successful > OK > Next.

12. It will run the pre requisite check again > when finished click begin install.

13. When finished click Next > Finish.

14.Now you need to send out the clients and configure SCCM, I’ll cover that in a later article.

Related Articles, References, Credits, or External Links

SCCM 2007 Initial Setup and Configuration

SCCM OSD Capture a Windows 7 Reference Machine

Office Install Error 1935

Posted on by

KB ID 0000399 

Problem

Seen while installing Office 2007 Enterprise On Server 2008 R2 (Don’t ask).

Error:
Microcyst Office enterprise 2007 encountered and error during setup.
Error 1935.An error occurred during the installation of an assembly component
{837Bf-1EB-D770-94EB-A01F-C8B389A1E18E}. HRESULT: 0x80070BC9

Solution

1. Essentially there is a .Net problem, On Server 2008 you will need to add in .Net as a feature. (Server Manager > Features > Add Feature > Locate and install .Net).

2. Follow the instructions, when finished run Windows Update to get the latest .Net service pack installed, then reboot.

3. Post reboot, it should install without error.

 

Related Articles, References, Credits, or External Links

NA

 

Installing Exchange 2007 On Windows Server 2008

Posted on by

(Greenfield site – No existing Exchange)

KB ID 0000268

Problem

Assumptions

You have an x64 Bit server (x32 is not supported for production). You have an x64 Bit copy of Server 2008 or Server 2008 R2.

Solution

Pre site visit

To save time onsite it may be worth (If remote connection is available) downloading the relevant install media and service packs beforehand.

Pre requisites

1. .net 2.0 – pre installed in Server 2008 and Server 2008 R2

2. MMC 3.0 – pre installed in Server 2008 and Server2008 R2

3. Powershell needs to be installed, its pre installed on Server 2008 R2, on Server 2008 do the following > Start > run > cmd {Enter}> enter the following command,

[box]ServerManagerCmd -i PowerShell[/box]

Note: It may look like it’s hung but after a while it will say “Success: Installation succeeded.”

4. You now need to add a server role > Start > Server Manager > Roles > Add Roles > IIS (Web Server) > Start > Server Manager > Roles > Add Roles > Next > Tick “Web Server IIS” > Next.

5. Security Section > Add Basic Authentication, Digest Authentication, and Windows Authentication.

6. IIS 6 Management Compatibility Section > Add IIS 6 Metabase Compatibility and IIS 6 Management Console > Performance section > Tick Static and Dynamic Content compression.

7. Click Next > Install > Close.

8. Now Select Features > Ad Features > Expand Remote server Administration Tools > Expand Role Administration Tools > tick AD DS and AD LDS Tools > Add Required Features > Next > Install > Close > Reboot when promoted.

9. Run Windows update.

 

Pre Install Tasks

Assuming you’re installing from CD/DVD (if not change E: to the correct path.)

If you are going to do the via RDP you MUST! Be on the console session.

1. From command line Execute the following command,

[box]E:Setup.com /PrepareSchema[/box]

2. When it’s done Execute the following command,

[box]E:Setup.com /PrepareAD /OrganizationName:{the_organisation_name}[/box]

3. When its done Execute the following command,

[box]E:Setup.com /PrepareDomain[/box]

Install Exchange 2007

I have on one occasion needed to copy all the DVD/CD’s contents to the server for Installation to be successful.

1. Assuming the CD/DVD from which you are deploying Exchange 2007 from is E: > Start > Run > CMD {enter}.

2. Execute the following command,

[box]E:Setup.exe[/box]

3. Click Step 4 > Introduction Screen > Next > Tick “I accept the terms….” > Next > Next > Select Typical > Next.

4. You will then be asked if you have and Outlook 2003 or earlier clients Answer Yes or No > Next.

5. Exchange 2007 will now do some checks > Click Install > When done > Finish >Reboot the server.

6. Launch the Exchange Management Console > Ignore any Licence warnings.

7. Select Server configuration > Select the new Server > Action > Enter Product Key > Type in your Key > Read the Warning > Finish > either reboot or restart the “Microsoft Exchange Information Store” service.

8. At time of writing SP2 is not supported on R2. But run Windows update to get any further updates/roll ups.

Error: This compuer is running Windows Server R2 Enterprise. Exchange Server 2007 is not supported on this operating system.

9. The new 2007 Organisation will have one mailbox database and one Public folder database (If you said “Yes” I have Outlook 2003 or earlier during install) > Expand Microsoft Exchange > Server configuration > Mailbox > Select the server > The Databases will be displayed in the center panel at the bottom.

10. You can select the databases > Right Click > “Move Database Path” to move them onto another partition.

11. Point SMTP Feed to the New Server, the MX Record should now be pointing to the public IP of the new server OR the Firewall SMTP Port re-directs needs changing to the new server.

12. Once the SMTP Feed has swapped across, inbound mail may fail and return the following error,

mail.domainc.com #530 5.7.1 Client was not authenticated ##

To fix that you will need to allow anonymous access on the servers default receive connector. > Launch Exchange Management Console > Server Configuration > Hub Transport > right click the “Default {server name}” connector > Permission groups > tick “Anonymous users” > Apply >OK.

5. You may also find outbound mail will fail, and sit on the outbound queue with the following error,

A matching connector cannot be found to route the external recipient

To fix that you will need to create a “Send Connector”. Launch the Exchange 2007 Management Console > Organization Configuration > Hub Transport > Send Connectors > New Send Connector > Give it a name and CHANGE the intended use from Custom to Internet > Next > Add > In the address box type a single asterisk * > tick Include all subfolders > OK > Next > Add a smart host IF you use one > Next > Next > New > Finish.

Install Antispam Agents

1. Start > All Programs > Microsoft Exchange Server 2007 > Exchange Management Shell.

2. Execute the following commands,

[box]

cd "c:Program FilesMicrosoftExchange ServerScripts"
./install-AntispamAgents.ps1
Net stop "Microsoft Exchange Transport"
Net start "Microsoft Exchange Transport"

[/box]

3. Stop and restart the Exchange Management Console (NOT the exchange Management Shell).

Note: If the antispam Agents are installed remove the following folder from the backup (Or it will error).

C:Program FilesMicrosoftExchange ServerTransportRoles

Post Install Tasks

1. You may need to exclude the following folder from the backup. C:WINDOWSMicrosoft.NETFramework64v2.0.50727CONFIG

2. If OWA displays “Service Unavailable” See here and run through the ASP.NET 2.0, 64-bit version section.

Related Articles, References, Credits, or External Links

NA

GNS3 – Error ‘ghostsize is to small for device’

Posted on by

KB ID 0000935 

Problem

While doing a quick lab in GNS3, I tried to add NAT to a router, and it fell over with the following error;

[box]

R3(config-if)#ip nat outside
% NBAR ERROR: parsing stopped
% NBAR Error : Activation failed due to insufficient dynamic memory
% NBAR Error: Stile could not add protocol node
%NAT: Error activating CNBAR on the interface FastEthernet0/0
R3(config-if)#
*Mar 1 00:01:11.655: %SYS-2-MALLOCFAIL: Memory allocation of 10260 bytes failed
from 0x62915CD4, alignment 0
Pool: Processor Free: 28660 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
-Process= "Exec", ipl= 0, pid= 93, -Traceback= 0x6148BFF8 0x60016604 0x6001C564 0x6001CBBC 0x636756E4 0x62915CDC 0x628F468C 0x628F9DA0 0x628F5968 0x628FA474 0x628F5968 0x628F8344 0x628F5968 0x628F5B2C 0x62928FBC 0x62933A20
*Mar 1 00:01:11.659: %NBAR-2-NOMEMORY: No memory available for StILE lmalloc, -Traceback= 0x6148BFF8 0x62915CF8 0x628F468C 0x628F9DA0 0x628F5968 0x628FA474 0x628F5968 0x628F8344 0x628F5968 0x628F5B2C 0x62928FBC 0x62933A20 0x62920BD0 0x6293DF70 0x6293E2F0 0x61C77C70
R3(config-if)#
*Mar 1 00:01:12.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface NVI0, changed state to up
R3(config-if)#

[/box]

A quick Google told me, this was because I didn’t have enough memory assigned to the router, and I was supposed to change this, save the new setting, and reload the router. But as soon as I did that, this happened. (Note: Seen in GNS3, I could not console to the router).

[box]

GNS3 management console. Running GNS3 version 0.8.6.
Copyright (c) 2006-2013GNS3 Project.

=> *** Warning: ghostsize is to small for device R3. Increase it with the ghostsize option.

[/box]

Solution

1. Locate the filename.net file for your project, and open it.

Note: Usually in C:Users{user-name}GNS3Projects

2. Locate the section that contains your router settings, (you should see the IOS image name). Below that change the RAM value, here I changed it from 128 to 256, then save the file and reopen your GNS3 project.

3. To stop this happening again, whilst in GNS3 > Edit > IOS Images and Hypervisors > Locate the router image, and set the default RAM figure here > Save > Click Test settings to make sure.

Related Articles, References, Credits, or External Links

NA