MFCOM Errors During Discovery Process in the Access Management Console for Custom Citrix Administrators

# Logon as the local Administrator
# Try to run the discovery process
# If it fails (as it did for me) open a command console
# Change directory to the following path: C:\Program Files (x86)\Citrix\Independent Management Architecture
# Type the following command: dsmaint config /user:administrator /pwd:Evaluation1 /dsn:"c:\Program Files (x86)\Citrix\Independent Management Architecture\mf20.dsn"
# For the password use your local administrator account password
# You will see the following output: \\ Attempting to connect to the data store with new configuration settings. \\ Successfully connected to the data store. \\ Configuration successfully changed. \\ Please restart the IMA Service for changes to take effect.
# Open Services in Admin Tools and stop the Citrix Independent Management Architecture
# Using the same command console type the following command: dsmaint recreatelhc
# Now restart the Citrix Independent Management Architecture service
# Try the discovery process again and it should work!

HOW TO: Enable the build-in Administrator account in Windows Vista and Windows 7

To enable the build-in Administrator account, follow these steps:
1. Click Start, and then type cmd in the Start Search box. 
2. In the search results list, right-click Command Prompt, and then click Run as Administrator. 
3. When you are prompted by User Account Control, click Continue. 
4. At the command prompt, type net user administrator /active:yes, and then press ENTER.  
5. Type net user administrator , and then press ENTER.
Note: Please replace the tag with your passwords which you want to set to administrator account. 
6. Type exit, and then press ENTER.
7. Log off the current user account.

Enabling Ping and Traceroute on the Cisco ASA 5505

Enabling Ping and Traceroute on the Cisco ASA 5505

Today I found some time to sit down and figure out why my ASA box was denying ping, traceroute and other ICMP traffic. Denying all ICMP traffic is the most secure option, and I think Cisco made a good choice by making this the default. However, I really wanted to be able to ping and traceroute from inside my network to the outside world, if for no other reason than to check the latency of my servers. Here’s how to do it in ASDM.

First, open an ASDM connection to your router. Go into the Configuration screens and click on Firewall to configure the firewall options. Then click on Service Policy Rules to configure the services that the firewall software will monitor. Select the global policy (first and only one in the list), and click on the Edit button. Switch to the Rule Actions (3rd) tab, and in the list check to enable ICMP. You can leave ICMP Error unchecked. Close that and Apply the changes.

Now, if you just want to be able to ping, stop here and you are done. However, traceroute will not work with this setup. For traceroute to work, you have to complete this follow-up task.

While still under the Firewall configuration switch to the Access Rules item. Add an access rule to permit ICMP traffic. Click the Add button, make sure the interface is set to outside, action is Permit, and Source/Destination is any. Under Service, click the … button and select the icmp line and click OK. Click OK again in the Add Access Rule dialog and Apply the results to finish the process.