February 2013

I am currently working on the following systems:

• Microsoft Multipoint 2011 Server with ZERO clients by WYSEThis setup consist of Windows 2008R2 Domain Controller and 6 Multipoint 2011 Servers. Incidentally, MP 2012 has been release.
• To protect the innocent, I will just tell you that this setup is best for Education environment Each classroom can have up to 25 ZERO clients connected to 1 Multipoint Server. The ZERO client is about 3″x3″x1/2″ square black box that has an Ethernet, 2 USB, audio/mic jacks, and a power connector. Once the Multipoint 2011 Server is up and the MP service is running, the ZERO clients will automatically get a Windows user name / password login prompt.
• The infrastructure consist of SOPHOS UTM220, this unit can do many things, google it, but I only have license for Basic, Web Filtering, & Anti Virus. There are predefined categories but I find it not useful at all. I will extract the configuration but really if you read the documentation provided, you can breeze through the configuration of this device. Have have been warn, it is very noisy device since I set it up near my desk
• The AD has almost can’t do anything kind of Group Policy defined due to its environment and hostile geniuses that think they can beat the systems. I will share with you the user logon scripts as soon as I have protect the innocent.
• Remote offices VPN using Sonicwall TZ200w. Configured to have a tunnel back to the main office including the Avaya IP Office 500 telephony system. Ah yes, that’s a complicated beast and it is similar to Interactive Intelligent for those of you have worked with IC3 before. Well in my opinion Avaya is much more complicated. These remote office has Avaya phone SIP connection to the main office, it can be dialed by an extension number.. When setting the VPN make sure all your PROPOSAL are matched, this is VERY important.
• Network NAS is being utilized at most of the clients site, SYNOLOGY You can enable SSH to this device as they are running a flavor of Linux. Poke a hole in your FW with a custom port number for safety and remotely monitor/administration the unit is a beauty.
• Windows RDP default port is 3389 which can be exploit so I would suggest you to add an entry in your registry key to enable a custom port. To do such thing, follow these instruction below:
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
  The above is the location of the key that you need to export, rename and import back in with the new defined name and port number. I would not suggest modify what’s there as the default. But hey if you feel venturesome, go right ahead but don’t say I didn’t warn you.

I am current learning the following:

• Configure & Install Avaya Office IP 500 (a beast!)