The Sysadmins

Tips and tricks from the Sysadmins

Category: General (page 1 of 2)

Remote Desktop iOS 8.1.0 – Error 0x03000008


In a recent update to the iOS Remote Desktop client (8.1.0 and above) you receive the following error when connecting using a Remote Desktop Gateway: Can’t connect to the Remote Desktop Gateway. Contact your network administrator for assistance. (Error code: 0x03000008)

iPhone iPad Error 0x03000008

Confirmed on the Remote Desktop Services blog here.


1. Review the TerminalServices-Gateway operational event log on the Remote Desktop Gateway server and look for EventID 301 which states: The user “DOMAIN\user”, on client computer “”, did not meet resource authorization policy requirements and was therefore not authorized to resource “”. The following error occurred: “23002”.


The resource IP should be one of your RDS servers, note healthy connections to the Gateway should (typically) specify the FQDN of the RDS server it is trying to connect to: The user “Domain\user”, on client computer “”, met resource authorization policy requirements and was therefore authorized to connect to resource ““.

Continue reading


Over the last couple of years I’ve started listening to more technical Podcasts. This initially stemmed from having to do more housework (!) but has spread to longer commutes or trips, especially in the car. I find it’s a great way, without having to pay too much attention to keep up to date with various topics and news.

I listen to a small handful of Podcasts regularly, so go and check them out.

Security Now
Windows Weekly
This Week in Enterprise Tech
Runas Weekly
Portforward Podcast

I tried a couple of Android applications to automate the download of new episodes without much success until I stumbled on a recommendation for Pocket Casts. It currently costs £1.99, and it’s the best Android application I’ve found for the job. I’ve set it to automatically download when a new episode is released and to only keep the last 2 episodes. You can also set the episode updates to occur only when using WiFi, which is great for those with more restrictive data tariffs.

Have a podcast to recommend? Please use the comments below.

View .pages File on Windows

I’ve had a few requests to open .pages files lately and found a nice and quick way to extract the .pages file to expose a PDF file which can be opened within Windows. The Pages file extension originates from Apple’s iWorks Pages application.

Right click the .pages file and extract with 7zip (or your favorite alternative).

Open the quicklook folder and open the PDF version of the .pages file, most of the files I’ve come across allow text to be copied from the PDF.

Apple iOS – Move contacts from “On my iPhone” to Exchange

The Setup

Apple iPhone syncing contacts with Microsoft Exchange server

The Issue

New contacts default to the “On my iPhone” contact group, which aren’t synced with the Exchange account. This could cause contact loss when upgrading or switching iPhones, or will cause missing contacts on multiple devices e.g. iPads. I came across this earlier when someone mentioned their upgrade had missing contacts (turned out to be over 40). iOS version 5 seems to set Exchange as the default contact group, I believe this effects iOS 4 and below. You can change it in this location:

Settings -> Mail, Contacts and Calendars -> Contacts – Default Account

The Solution

There are a few paid apps that can move contacts across the groups, or another popular solution is to “share” the iPhone contact and email it to yourself, from there you can save it as a contact in the right group. After a bit more digging I stumbled across Orbicontact which was free is only £0.69/$0.99 and has the functionality needed.

OrbiConact – iTunes

The contacts should now appear in Outlook and/or the new iPhone.

WARNING 23/02/17

The move function of this application has been reported to copy the contact name without the number resulting in data loss. Please use the copy method or look for an alternative application.

Data Protection Manager 2010 – Long Term Backups Not Following Schedule for the Protection Group

We use System Center: Data Protection Manager for backups. On February 1st of 2011, the annual backup of one of my protection groups was running. Since it was scheduled for January 1st, I was a bit confused. I opened a ticket with Microsoft support and thus began a very long adventure into the DPM scheduling agent. The end result is that the issue is a bug triggered by an interaction between DPM and SQL Server that can be triggered under specific conditions that causes the behavior above.


Modify a protection group that has a long term retention schedule that is on anything other than a weekly or monthly basis and NOT adjust the timing of those backups.


The job is recreated in the SQL Server Agent without modifying the Start Date. This will cause it to trigger inappropriately, by running when it shouldn’t as well as failing to run when it should. This is due to the fact that although the start date didn’t change, the last run date is lost. Since the jobs are actually configured to run on X date (or day of the week/month/year) every x period of time instead of exact dates, this means my January 1st run date is configured as run on the 1st of the month every twelve months. Because of this it runs on the 1st of the next month if I trigger this bug.


How can you confirm this issue is going to happen to you? The easiest way is to use a script I was provided by Microsoft Support. A copy of the script is in the zip file available here.

The first time I ran the script I got an error. I re-ran it however, and it executed properly. I was told this is a bug in the script as it is currently defined. The output will look something like this:

Name SQL Agent Job Definintion ID Protection Group Start Date Schedule Create date/time Last run date/time Next run date/time Tape_Label Time Zone
GUID GUID PGName 06-30-2011 2011-06-30 09:09:37.130 01-21-2012 23:00:00 01-28-2012 23:00:00 Weekly Ignore
GUID GUID PGName 07-01-2011 2011-06-30 09:09:36.173 01-01-2012 23:00:00 02-01-2012 23:00:00 Monthly Ignore
GUID GUID PGName 01-01-2012 2011-06-30 09:09:35.133 01-01-2012 23:00:00 01-01-2013 23:00:00 Yearly Ignore

This is an example of one of my protection groups. Fields in italics have been altered to anonymize the data. The text in red is the one that is likely to have the issue. Should I modify this protection group at this time without entering the Modify Schedule dialog it WILL end up running a backup on the 1st of the following month since the start date is in the past.


As of now, there is no fix for this behavior. There is, however, a way to work around it. As mentioned in the Trigger section this only happens when you don’t open the modify schedule button. So what happens if you do? The Start Date is reset and the entire schedule will run as planned. When editing a protection group and you get to this screen:


You need to click on the Modify button on the Backup Schedule area so you get this screen:


Click OK on this screen to close it out. As long as do this the Start Date for the backup schedule will be reset so that it is correct. This will avoid triggering the bug and keep your backups on schedule.


At this time Microsoft has indicated that a script to fix this will be given to me in the relatively near future once they have the bugs worked out. Additionally either in DPM 2012 or DPM 2012 SP1 this issue will be resolved so the scheduler no longer causes this issue. At this time, they are unsure if the bugfix will be ported back to DPM 2010.

Greenshot – Screenshots Made Easy

I find myself taking a lot of screenshots, especially for things like documentation, sharing information or simply recording information on-screen. In the past I’d printscreen or use alt+printscreen (captures the active window), paste it into, adjust as needed and save. Whilst this method certainly worked it was a bit clunky and didn’t always provide the most professional looking screenshots.

Introduce Greenshot. I was a bit unsure how helpful this application would turn out to be, but I can say after a few months of using it- wow! It’s a great time saver and increases the quality and ease of taking screenshots.

Once the program is installed the Printscreen key defaults to selecting a region, which is great- I rarely need to take a screenshot of my entire screen… especially as I have dual screens in most places. You can of course capture the entire screen if you like with Ctrl + Printscreen, or if you’d like to capture the active windows alt + Printscreen also works.

There are various ways to output the image, including different image formats. My personal preference is to copy the image to clipboard and save it directly to a screenshot folder.

GreenShot Settings

Greenshot also includes it’s own inbuilt image editor, which includes annotating, highlighting or obfuscating parts of a screenshot.

Download Greenshot here.

Sage 50 Accounts – Reset Data

If a user forgets which client they currently have loaded or cannot remember the username or password there’s no easy or obvious way to reset the data or find the details.

This little tip will allow you to reset the current client and will allow you to restore a backup or create a new client, it will not allow you to recover the password or gain access to the current data. I probably come across this once a week so I decided to put together some basic batch scripts so the users can resolve the issue themselves.

I’ve included scripts for 2012 covering Windows XP and 7, you can easily modify the scripts to allow for older/new versions. Just change the year in the path C:\Documents and Settings\All Users\Application Data\Sage\Accounts\2012\company.000 or C:\ProgramData\Sage\Accounts\2012\Company.000.

This is based on a single user license, if you have a multi user license with multiple datasets you’ll want to manually go through this process and see which needs resetting.

Sage 50 Accounts 2012 – Windows XP

REM Accounts 2011 Dataset Reset.bat
@echo Removing dataset for Sage Line 50 Accounts 2012. Please make sure the application is closed.
@echo Off
REM Removes the .old ACCDATA if script has already been run
rmdir /s /q "C:\Documents and Settings\All Users\Application Data\Sage\Accounts\2012\company.000\ACCDATA.old"
REM Delay to allow for deletion
PING -n 5 >NUL
REM Renames the current ACCDATA
rename "C:\Documents and Settings\All Users\Application Data\Sage\Accounts\2012\company.000\ACCDATA" "ACCDATA.old"
REM Creates a new ACCDATA Folder
mkdir "C:\Documents and Settings\All Users\Application Data\Sage\Accounts\2012\company.000\ACCDATA"
REM Renames the company file, this will get recreated when a backup is restored or new client is setup
rename "C:\Documents and Settings\All Users\Application Data\Sage\Accounts\2012\company" "company.old"
@echo Complete! You can now open the application.

Sage 50 Accounts 2012 – Windows 7

REM Accounts 2011 Dataset Reset.bat
@echo Removing dataset for Sage Line 50 Accounts 2012. Please make sure the application is closed.
@echo Off
REM Removes the .old ACCDATA if script has already been run
rmdir /s /q "C:\ProgramData\Sage\Accounts\2012\Company.000\ACCDATA.old"
REM Delay to allow for deletion
PING -n 5 >NUL
REM Renames the current ACCDATA
rename "C:\ProgramData\Sage\Accounts\2012\Company.000\ACCDATA" "ACCDATA.old"
REM Creates a new ACCDATA Folder
mkdir "C:\ProgramData\Sage\Accounts\2012\Company.000\ACCDATA"
REM Renames the company file, this will get recreated when a backup is restored or new client is setup
rename "C:\ProgramData\Sage\Accounts\2012\company" "company.old"
@echo Complete! You can now open the application.
Older posts