Changing a computers asset tag in the MDT database

My brother (Stefan van Bruggen) wrote this function for me. I will be using this function in my script(s) that I’m writing to allows my customers and co-workers to add and change various information without manually manipulating the MDT SQL database.

The script uses the MDTDB module created by Michael Niehaus (which can be found HERE). This module allows you to change a lot of information in the database except for the asset tag.

Add this to the MDTDB.psm1 to be able to change the asset tags and the other scripts, which I will post on here soon.

 

T-Mobile Thuis Fiber with EdgeRouter Lite

The amount of configuration information on T-Mobile Thuis fiber connections with EdgeRouter equiptment is a bit scarce. The configuration looks a lot like the KPN Fiber and Vodafone configuration, but is slightly different.

I have chosen to use a fiber to ethernet converter, the TP-Link MC220L. But I think that I will buy the new EdgeRouter 4 when it comes to the Netherlands. Which is roughly the EdgeRouter X with fiber port and the EdgeRouter Lite combined. But for now, this configuration is based on the EdgeRouter Lite 3.

T-Mobile and their VLAN’s

At first, we need to know that T-Mobile seperates the internet and IPTV connection using VLAN’s. VLAN300 is used for the internet traffic and VLAN640 is used for the IPTV traffic. T-Mobile seperates this traffic in their own router. We will have to do the same in our configuration. Later on, we will devide our connection using a bridge in to two seperate VLAN’s. These VLAN’s will be made available in the switches.

My set-up

My set-up is fairly basic. In the diagram below, I have drawn out my setup. Let me talk you through it; The fiber connection comes in at the fiber converter and is attached to the ETH0 interface of the EdgeRouter-Lite (ER-L). The LAN connection is on ETH1 and is connected to an managed ethernet switch. The ETH2 is (in my case) directly attached to the IPTV box.
The switch has (multiple) Ubiquiti UniFi access points attached, a few wired devices (laptop, Ikea Tradfri gateway, a computer) and a (trunk) connection to another managed switch in the living room for my Playstation, TV and HTPC.

 

The configuration of the EdgeRouter Lite

Below here is a copy of my configuration, with a few details cleared. These are port mappings, static IP assignments and passwords. What this configuration does is the following:

  1. Create ETH0 for the WAN connection, with DHCP enabled so it receives it’s (external) IP from T-Mobile
  2. Split ETH0 in to ETH0.300 for the VLAN300 and ETH0.640 for the VLAN640 traffic (internet and iptv)
  3. Creathe ETH1 with local IP adresses in the 192.168.0.0/24 range. ETH1 has VLAN300 attached for the internet traffic.
  4. Creathe ETH2 without an IP adres (T-Mobile will handle that itself) with VLAN640 attached for IPTV.
  5. Create a few default firewall rules to block harmful traffic.
  6. Allow NAT for VLAN300 for the internet traffic
  7. Enable an IGMP proxy for IPTV

Read More

Citrix Director: ‘Cannot retreive the data’ after CU2 update

After installing the Citrix Director CU2 release (7.6.2000), I received the error ‘Cannot retrieve the data‘ when viewing information like connected sessions, logon duration and Virtual Desktop details. I have seen this error after updating to CU2 at two customer sites, both sites are enterprise hospital environments. I have not seen this error at testing environments and our own company environment.
Viewing the licensing status in Director is working perfectly fine.  Viewing logged in users is fine to, but viewing virtual desktop details wasn’t working.

Next to updating Citrix Director to the CU2 release, I have also updated the Delivery Controllers, License Server and Storefront to CU2.

There were a small amount of users that had no issues with Director and did not receive any error message. Most of them had an admin account and a user account. The user account was working fine. I made a clone of my own user account, deleted some AD groups and the errors were gone in Director. The users that had the error message all were IT users with a lot of (nested) groups, mostly more than 300.

Citrix Director looked like this after the update:

The event viewer on the server where Director is installed showed the following error:

After having contact with Citrix Support and reviewing the Citrix Director trace files, we saw that Director fails with HTTP Error 400.The size of the request header is too long. This is because Director machines is not able to retrieve any information due to bloated kerberos ticket.

We were able to fix the Cannot retrieve the data error by setting the following registery keys (DWORD) on both the Citrix Delivery contoller(s) and the Storefront server(s). The servers required a reboot after setting these keys.