After around three months of installing various software that uses SQL Server 2005 on my ESX server, my SQL VM finally reached it’s disk limit. I was poking around in the command line for the actual ESX server, and found a tool called vmkfstools that could do the job for me. You can resize the disk by running the command:

vmkfstools -X <size-in-mb>M <image-file>

So for example if i wanted to resize the file server.vmdk to 60GB, I would run:

vmkfstools -X 60000M server.vmdk

That was the easy part. Now I booted into Hiren’s BootCD (you can find this on the net), and ran Acronis Boot Manager to resize my partition. You can alternatively boot into the Recovery Console for Windows 2003/XP or run the Command Line on Windows Vista/2008 and run diskpart to accomplish the same thing.
That went all well and my disks were properly resized…. or so I thought, till I was greeted with the following message on boot:

Winload.exe?! Well scared that my OS was corrupt, I booted into the Windows 2008 Server CD and ran the command prompt. dir C:\ still showed all my files there, and C:\Windows\System32\ still had winload.exe in it. Just for shits and giggles, I replaced the file with the one in X:\Windows\System32 and tried rebooting.

Still didn’t work.

I booted back into the install DVD, clicked “Repair Computer”, but this time I noticed that my disk size was 0, and it said “Unknown” next to the disk. My gears were turning, and I realized that this might mean that my MBR was corrupt. Running bcdedit.exe /v confirmed that. Instead of saying:

device partition=C:

it said

device unknown

Recalling what I did a year a so back when my MBR was corrupt, I ran the following commands:

bootrec.exe /FixMbr
bootrec.exe /FixBoot
bootrec.exe /RebuildBcd

As soon as I rebooted, my system booted up without any issues!

Hope this helps anyone else this has happened to,

Brennan

When using SharePoint with a proxy server such as ISA, you will need to configure SharePoint Alternate Access Mappings (AAM) if the external address and the internal address are different. For example, if your internal address is http://wssserver/ and your external address is http://wssserver.domainname.com/. Here is a simple guide to configuring AAM on MOSS or WSS Server.

1. Open up your SharePoint Central Administration on the server running SharePoint.
2. Navigate to Operations under Central Administration.
3. Open up Alternate access mappings under Global Configuration
4. Click Edit Public URLs
5. Select your Alternate Access Mapping Collection (your web application)
6. Then enter the respective URLs that the application will be accessed via.
7. I usually do an iisreset /noforce after this.

I found that the other tutorials on the internet wern’t straight to the point, and it was hard to understand them. Hopefully this clears things up for Sharepoint novices out there!
Brennan

I recently was required to install BlackBerry Enterprise Server (BES) on our corporate network. I did the usual configuration following the step that I found on the BB site here.
I then proceeded to make an ISA Firewall Rule that enabled outbound acccess from the bes server (a computer object) to external on port 3101. I also created the corresponding inbound rule on port 3101 as well just to be extra sure.
I followed the steps word for word (or so I thought), and tried syncing a BlackBerry to the servers, and it just timed out on me. So then I went back to the drawing board, and realized that I didn’t setup my permissions on the Active Directory (AD) user accounts properly. So I uninstalled the server, followed the following steps:

1. Local Administrator rights on the BlackBerry Enterprise Server
2. Local Security Policy permissions for the BlackBerry Enterprise Server service account
3. Microsoft Exchange permissions at the Administrative Group level
4. Microsoft Exchange permissions at the Microsoft Exchange Server level
5. Send As permission at the Domain level
6. Database permissions for managing the BlackBerry Configuration Database

And reinstalled the server. Still no avail. I looked into the logs and noticed this line in the BES_DISP logfile:

IPPa] {User Name} Forwarding status to BES Agent (S61887304_001), intTag=5, extTag=1
[30222] (03/20 16:20:19.482):{0×898} {User Name} MTH: contentType=OTAKEYGEN, sizeOTA=216, sizeOTW=216, TransactionId=-941432706, Tag=2
[30310] (03/20 16:20:19.482):{0×898} {User Name} Forwarding internal data to device, contentType=OTAKEYGEN, routing=S61887304, device=301D4AC4, size=258, cmd=0×3, ack=0, TransactionId=-941432706, intTag=8, Tag=2, Submit=1
[30375] (03/20 16:20:19.576):{0×8A0} {User Name} Packet returned as FAILED – could not be delivered to device, Tag=2

After doing some research, I found out that you NEED to have the BES option on your phone which can only be set by your carrier. To find out if you have this or not, just go to options -> advanced settings and see if theres an option for Enterprise Activation anywhere. If there isn’t, that means that you do not have the BES package. To get this, just phone your carrier, and ask them to add BlackBerry Enterprise Services (BES or pronounced B’ezz) to your account and you should be good to go!
Brennan

Another one my wonderful fixes/tutorials on what Microsoft should have flippin documented in the first place. But I guess they can’t test and document everything eh?
Well heres how you get ISA 2006 and Outlook Anywhere with Exchange 2007 to work nicely using NTLM Authentication.

WARNING: You must have OWA and Outlook Anywhere running on different web listeners.

1. First Configure your Firewall Rule authentication method to “No authentication, but client may authenticate directly”
2. Then set your Web Listener to HTTP Authentication with Basic and Integrated authentication methods selected.
3. Go to the Exchange Management Console and make sure that Outlook Anywhere is set to NTLM Authentication mode. You can do this under the “Server Management” area.
4. Go to the IIS Management Console, and make sure that Integrated Authentication is enabled for your Outlook Anywhere Web Site (usually “Default Web Site”)
5. Switch over to NTLM Authentication in Outlook, and you should be rockin!

By the way, this isn’t as secure as using Basic authentication because ISA is just passing the session through to the Exchange server, and not proxying everything. But I’d say not having to type your password everyime is worth that sacrifice.
Brennan

Some of you may be having a hard time configuring CRM 4.0 and ISA 2006. All seems well when you use the web client, but when you try to configure your Outlook Client, you get:

“The request failed with HTTP status 401: Unauthorized ( The server requires authentication to fufill the request. Access to the Web server is denied. Contact the server administrator. ).”

I finally found a solution(s)!

Method 1:

1. Run the following SQL command (replace addresses with yours (address:port)

   USE MSCRM_CONFIG

   Update DeploymentProperties SET NVarCharColumn = ‘my.crmserver.inet:80′ WHERE       ColumnName = ‘AsyncSdkRootDomain’

   Update DeploymentProperties SET NvarCharColumn = ‘my.crmserver.inet:80′ WHERE  ColumnName = ‘ADSdkRootDomain’

   Update DeploymentProperties SET NvarCharColumn = ‘my.crmserver.inet:80′ WHERE ColumnName = ‘ADWebApplicationRootDomain’

2. Run regedit on the CRM host computer, and navigate to HKEY_CURRENT_USER\SOFTWARE\Microsoft\MSCRMClient. You now have to update the following keys
   • IntranetDiscoveryUrl
   • IntranetServerUrl
   • IntranetWebAppUrl
   • PlatformRoot
   To point to your External CRM URL.
3. Enable just Basic HTTP Authentication on the Web Listener in ISA
4. In the Authentication tab of the Firewall Policy for the CRM, select “No authentication, but client may authenticate directly”.
5. In the To tab of the Firewall Policy for the CRM, make sure “Foreward original host header” and “Requests appear to come from the original client” is selected.
6. In the Users tab of the Firewall Policy for the CRM, make sure it is “All Users” Instead of “All Authenticated Users” (CRUCUAL STEP)
7. Apply the settings in ISA.
8. Now go to “Internet Settings” on the client computer, and navigate to the security tab.
9. Click custom level on the trusted site, and scroll to the very bottom and select “Automatic logon with current user name and password”.
10. Add the CRM url to the trusted sites without the prefix (aka. not http://crm.company.com and just crm.company.com).
11. Navigate to http://crm.company.com and type in your login credentials. AND CLICK REMEMBER PASSWORD.
12. Run the configuration wizard, and it should work *smile*

Method 2:

1. Download the Internet Facing Tool from Microsoft.
2. Extract the downloaded file to drive:\Program Files\Microsoft Dynamics CRM\Tools
3. Run the tool.
4. In the IFD boxes, type in your EXTERNAL URL and in the internal box, type in your INTERNAL URL.
5. Select whether to use HTTP or HTTPS for both the IFD Address and Internal address.
6. Apply, and reboot!
7. Now go to “Internet Settings” on the client computer, and navigate to the security tab.
8. Click custom level on the trusted site, and scroll to the very bottom and select “Automatic logon with current
9. user name and password”.
10. Add the CRM url to the trusted sites without the prefix (aka. not http://crm.company.com and just crm.company.com).
11. Navigate to http://crm.company.com and type in your login credentials. AND CLICK REMEMBER PASSWORD.
12. Enjoy!

If you don’t have any internal users, I’d recommend using Method 1, and if you want SSL and/or want to differentiate between external and internal users, use Method 2.

Brennan