1. Create a new GPO if necessary, link it to the OU where it needs to be applied
2. Edit the new GPO, and go to Computer Configuration, Preferences, Control Panel Settings, Local Users and Groups
   
3. Right-click in the pane on the right, and select New, Local Group
4. Set up the “New Local Group” as per below. I’ve got it removing all existing users and groups so that we can define everything we need using Group Policy. You add variables like %computername% by pressing F3 whilst the cursor is in a text entry field.
    
   I also included the Description text that is shown on the default local Administrators group; "Administrators have complete and unrestricted access to the computer/domain”
    
5. You also need to add a member called “domainname\%ComputerName%-Admins”. This will allow you to define a group in AD that can be used to assign local admin rights to a particular machine.

   The good thing about this is that you only need to define groups for PCs that you wish to add local admins to, but all PCs that have the GPO applied are ready for this type of setup.
   

6. You can also go into the Common tab and select “Remove this item when it is no longer applied”
   
7. The last step is to create a Security Group in AD with the name {computername}-Admins. For example, if you have a computer named syd-60128, you create a group in AD called syd-60128-Admins. Adding users into that group will then make those users a local administrator for that particular PC.
8. Do a “gpupdate” on the machine in question, and you should see the group’s membership change:
   

I’ve yet to see a good event calendar in any of the CMSes I’ve tried that properly handles recurring events and makes it easy for the layman to update calendar events. I’ve therefore recently implemented a small macro for Umbraco that displays Google Calendar events from a cached XML calendar feed. I did this using the excellent FeedCache plugin and some XSLT.

My one gripe with FeedCache is that you can’t edit the feeds.config file using ConfigTree, but rather need file-level access to it. This is a major bummer, as I wanted to test it on Umbraco Trials.

I won’t post any CSS, but the XSLT caters for styling as it uses bulleted lists and spans around key areas.

The feed will then be displayed similar to below:

Today

* Test Event (19:30-21:30)

Friday 16th October

* Meeting (19:30-21:30)

Sunday 18th October

* Seminar (10:30-12:30)
* Lunch (13:00-14:00)
* Games/Activities (14:30-15:30)

Here’s a screenshot of it working on an Umbraco Trials site. I found a random Google Calendar feed and used that for the demo. Note that I didn’t put any effort into styling the results:

Basically, what you need to do is:

1. Install FeedCache
2. Install the GCal Events List package
3. Set up the calendar feed in FeedCache’s feeds.config. The feeds.config entry should look like this:

   <feed>
    <url><![CDATA[http://www.google.com/calendar/feeds/calendar@example.org/public/composite?orderby=starttime&sortorder=ascending&futureevents=true&singleevents=true]]> </url>
    <localFile>GoogleCalendarFeed.xml</localFile>
   </feed>

4. Insert a macro wherever you need it, and fill out the parameters;
   1. numberOfDays – (integer) how many days worth of events you would like to display
   2. xmlFileName (string) the exact file name of the cached XML file in the umbraco\plugins\FergusonMoriyama\feedcache\ folder. eg. googleEvents.xml
5. Call FeedCache from your browser to trigger a pull of the feed(s): http://example.org/umbraco/plugins/FergusonMoriyama/FeedCache/FeedCache.aspx
6. View the page that contains the macro inserted in step 4.

Below are some instructions found on the forum, and the rest of the process that I followed:

1. Download patched DLL
2. Run a Command Prompt as an Administrator, and run the following commands:
   1. takeown /a /f %SystemRoot%\System32\termsrv.dll
   2. icacls %SystemRoot%\System32\termsrv.dll /Grant Administrators:F
3. Stop the Terminal Services service (Windows Key + R, services.msc)
4. Rename the original termsrv.dll (in %systemroot%\system32) to termsrv.dll.bak
5. Copy the patched dll into place
6. Run Registry Editor (Windows Key + R, regedit)
7. Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
8. Change the following 2 items:
   1. fDenyTSConnections – New value: 0
   2. fSingleSessionPerUser – New value: 0
9. Start the Terminal Services service

Below is a screen shot of it working on my home PC.

Don’t contact me for help in getting this running, or if this procedure breaks your PC.

If you’re not keen on doing this, an excellent alternative is LogMeIn’s free remote desktop solution.

Here are some things you may need to consider (outside of the obvious like DHCP scopes, DNS server settings, Firewall settings & rules, etc) when changing the IP range your Windows network operates on:

• TCP/IP Printer ports on print server
• Printer/Copier IP/DNS/SMTP settings
• Exchange allowed relay ranges
• Any copy/print accounting devices attached to copiers
• Monitoring host settings. Eg. Big Brother/Hobbit – Both client and server side, if not configured to use DNS in config files
• Server iLO IP addresses

Some steps for changing domain controller IP addresses. Do these first before any other important servers:

1. Change IP
2. ipconfig /flushdns
3. ipconfig /registerdns
4. Either restart the Netlogon service, or run ‘nltest /dsregdns’
5. Reboot

Disclaimer: This is by no means a complete list. Use these directions at your own risk.

What does this mean?, you say. It means you’ve got one neat console where you can manage all your remote connections in one place. mRemote currently supports these protocols:

• RDP (Remote Desktop)
• VNC (Virtual Network Computing)
• ICA (Independent Computing Architecture)
• SSH (Secure Shell)
• Telnet (TELecommunication NETwork)
• HTTP/S (Hypertext Transfer Protocol)
• Rlogin (Rlogin)
• RAW

I haven’t set it up fully yet, but it will be really handy to have all my web-based admin areas and SSH to Linux boxes in there too.

A side note, it uses the same rendering engine as Firefox, so some web-based admin pages may not display properly. This, however is no fault of mRemote or Firefox’s.

It can be done by simply creating a transform (MST) file using Orca. This is advantageous over importing the MSI into Advanced installer for the following reasons:

1. You’ll be using MYOB’s original MSI file
2. You don’t need to make any changes to the MSI file itself. All changes are specified in the transform file.

This will install Premier to the root of C drive, which is MYOB’s default location. For example, Premier 11 will be installed to C:\premier11.

You’ll need Orca installed. Instructions for Premier 12 are below. For Premier 11, follow the same instructions – but take note of point 4.2.2

1. Copy the default MSI and CAB files from the CD to your deployment share.
2. Right-click the MSI and choose “Edit with Orca”
3. Go to the Transform menu, and select “New Transform”. Any changes you now make to the MSI will be effected in a separate “MST” file.
4. Make the following changes:
1. In the CustomAction table:
   1. Select “ISVerifyScriptingRuntime” and press delete (or right click on it and choose “Drop Row”
   2. Do the same for ISSetupFilesExtract
   3. Do the same for ISSetupFilesCleanup
2. In the Directory table:
1. Change directory “KEY_NAME_SC” DefaultDir to “MYOB|MYOB” (without the quotes)
2. If deploying Premier 11:
1. Change directory  “ISYourCompanyDir” to MYOB|MYOB
2. Change directory “ISYourProductDir” to PREMIE~1|Premier11
5. Go to the Transform menu, and select “Generate Transform”. Save the transform file into the same network share/folder as your MSI and CAB file
6. You’re now ready to deploy Premier. Ensure you take note of the key points below:
   1. Make sure you choose the ‘Advanced’ Deployment Method, when you start adding the package to the policy.
   2. Assign the software package to the computer, in the “Computer Configuration” section of the policy.
   3. In the “Modifications” tab, make sure you specify the transform file that we created above.
   4. In the “Deployment” tab, be sure to check the “Uninstall this application when it falls out of the scope of management” checkbox.

If you’re not experienced in deploying software via MSI, the following links may be useful:

• How to use Group Policy to remotely install software in Windows Server 2003: http://support.microsoft.com/kb/816102
• How to assign software to a specific group by using Group Policy: http://support.microsoft.com/kb/302430/

foreach ($this->data[$this->name] as $key => $value) {
    if (!set::classicExtract($this->data,$this->name . '.' . $key)) {
        $this->data = set::remove($this->data,$this->name . '.' . $key);
    }
}

I use it where the DB may be expecting values for certain fields that are optional in the UI, and therefore may be returned empty by the controller.