Forefront TMG console on Windows 8 CP failed with error 0x80020003

As I’m testing Windows 8 CP in production environment for a week or two I had an “old” problem with Forefront TMG 2010 console

After installing Forefront TMG console I’m receiving error 0x80020003

This error occurs in past when you are upgrade IE or when you are install SP1 for TMG

Workaround for this error is:

1. Open TabsHandler.htc in C:\Program Files\Microsoft Forefront Threat Management Gateway\UI_HTMLs\Tabs Handler folder

2. Search for the 3 lines which contain “paddingTop“, and remark-out each of them by adding “//” in the beginning.

Example: Change the line: m_aPages [niPage].m_tdMain.style.paddingTop = ((m_nBoostUp < 0) ? -m_nBoostUp : 0) into: // m_aPages [niPage].m_tdMain.style.paddingTop = ((m_nBoostUp < 0) ? -m_nBoostUp : 0)

3. Save the file, and reopen Forefront TMG 2010 management console.

Your Forefront TMG management console working fine now.

Advertisements

Problem with intranet web and TMG 2010

I had very tight schedule last month, month and half

At first I had to prepare two presentations for two conferences. And second I had to configure my TMG that users have access to intranet web page.

From first it looks like simple configuration but later I couldn’t open intranet web page.

My configuration was simple. Intranet is on LAN not in DMZ, and TMG for some reason were blocked web access to every web page in LAN.

I tried to avoid configuring proxy settings using GPO. I want to use Firewall Client but firewall client deletes all exception distributed by GPO

Situation was pretty annoying.

Then I discovered WPAD (WebProxyAutomaticDetection).

I configured WPAD in next steps

1. In DHCP I was right clicked IPV4 then choose Set Predefined Options

WPAD1

2. Clicked Add

3. IN name box I typed WPAD

4. For Data Type choose String

5. In Code type 252

6. Then click OK

WPAD2

7. Right click again on IPV4 and choose again Set Predefined Option

8. Choose option 252 WPAD

9. In String put http://FQDNservername:8080/wpad.dat

10. Click OK

WPAD3

After this I just add option 252 to be distributed by DHCP and wait.

Second thing was few configurations on TMG 2010

WPAD5WPAD4

My users now have access to intranet web page but this wasn’t desired configuration for me

My first idea was that only use firewall client but I had problems with intranet web access. Currently this automated solution works fine but I will see how to use only firewall client.

What to do if your Hyper-v admin shares wont work

At friday had strange situation. I was installing my new Hyper-V server, and I had problems with migration. I was exported machine with Hyper-V manager but i couldn’t copy it to new Hyper-V server.

Why? I couldn’t reach admin shares (C$, D$) to copy virtual machine for import. I set up everything, checked firewall twice but problem was still here.

Then I think about solution to enable file and printer sharing.

And how to do that at Hyper-V? Because Hyper-V is Core OS any you don’t have all nice mmc plug-in for firewall setup.

You must do that using Command Prompt.

Syntax for this is:

“netsh firewall set service fileandprint”

After this all shares is accessible and i was completed my migration (import) to new Hyper-V machine.

Installing Hyper-V 2008 R2 SP1 on IBM X346 with ADAPTEC SCSI u320 controller

It could be pretty tricky to install Hyper-V 2008 R2 SP1 on IBM x346 with Adaptec controller. If didn’t want to throw away my old server so I decided to install Hyper-V on it to create testing environment.

I do this with colleague of mine, and we faced with problem. Hyper-V wont install on IBM x346. Why? Server asked for driver….

I think that driver is so old that Hyper-V don’t have it in its drivers database, and You can’t install it using ServerGuide CD.

What were we do.

After spending hours trying to install Hyper-V on IBM x346 with Adaptec u320 SCSI controller, finally we have solution.

My colleague Luka Gros spend finds x64 driver for Adaptec SCSI controller. He found it on this link.

After downloading, you must extract this driver and burn it on CD

Steps what we are do after that is:

booting from Hyper-V 2008 R2 SP1 and starting installation

when asked for driver change CD to one with driver and click Browse

find driver on CD and click Next

change CD to installation CD again and finish your installation

Hyper-V is installed and running fine now

Smiješak

P.S.

If You need to manipulate with physical HDD on your Hyper-V, MMC console will return error “RPC server unavailable”.

To avoid this run this command with elevated privileges:

netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes

Thanks to Luka Gros