Windows Server 2008 – Permanent Network Share Mapping

I recently found the need for permanently mounted network shares on a Windows server. Not an obvious thing to do, unfortunately…

What do I mean by permanent? When mapping a share on Windows as a user, when that user logs off… the share will disconnect. For an installed Windows Service that requires access to defined network shares – this is unworkable. We need to create network shares that retain their connection no matter whether or not a particular user is logged on.

Why do I need to do this? For a server-based AIR project ;D

Took a lot of searching – but here is how to do it!


First, we need to get into the Windows Server Group Policy Editor. The simplest way to access this is to type “gpedit” into the start menu search. The Group Policy Editor will now appear.

Using the left navigation menu, drill down through Computer Configuration > Windows Settings > Scripts (Startup/Shutdown). Double-click on Startup to open the Startup Properties dialog.

From the Scripts tab, we will want to click on the Show Files… button to open a File Explorer window.

Right-click in this window to create a new text file called mapping.bat (or whatever you want to call it). This needs to be a .bat file though to execute commands properly.

Edit the file and add the following lines of code:
net use m: \\servername\share

Add one command like this for each share you wish to add.

Now, return to the Startup Properties dialog and click Add… to browse to and select the .bat file we just created. It will appear in the list of startup scripts.

Exit the dialog by clicking OK.

You’ll now need to restart the server for this to take effect. This will allow the startup process to run the required commands to mount these network shares without any user being logged on.

Packaging AIR 3 Captive Runtime for Windows Distribution

This is the first post of 2012 and an attempt to get the year started off well! I wasn’t able to post nearly as much “useful” information in 2011 since I was tied up with so much other stuff… but am definitely working toward changing that by producing more content like this. Happy New Year, all!

Adobe AIR 3 allows a developer to package an AIR app along with the AIR runtime for distribution. This is known as “captive runtime” and is useful because it provides a method of application distribution that does not require a separate runtime installation. With Windows, an additional step must be taken; we have to package the application files into a custom installer for the best user experience on that platform. Thankfully, to do this is a fairly simple task as demonstrated in the recording below.

Here’s an additional recording on other options within Advanced Installer:

Windows 7 RC Impressions

Unlike the majority of reports out there, I’ve never had a major problem with Windows Vista. The two big problems I have had are in regard to the difficulty in taking ownership of files and directories even when logged in as an admin, and the initial lack of drivers. The first problem is remedied with some basic re-education, and the second issue has been resolved for some time now due to availability. My only major gripe is not with Windows but lies in the fact that Microsoft feels the need to stick its nose into everything under the sun (Silverlight, for example). Windows Vista has been a fine experience for me in the three years I’ve been using it.

I’ve been using the Windows 7 beta on my laptop since it was released months ago, and recently switched to the RC build. I’m very impressed with the changes from Vista- so much so, that I’ve now upgraded my home office machine to the Windows 7 RC. This is no small step as I’m dependent on this system for all my consulting, development, and audio production duties. This is how much I favor Windows 7 over Vista- it is such a refined user experience, overall. The reliability and speed improvements on older machines are a huge plus as well… that laptop I mentioned previously was purchased in 2004.

Here’s a short video demonstrating some niceties in my current environment:

Get the Flash Player to see this content.

My Favorite New CS3 Feature (sarcasm)

The installer for CS3 Web Premium is horrible! This is a consistent experience across machines. In an attempt to install the product on a fresh copy of Windows XP, I’ve had to run the installer about 5 times now. I’ve had similar experiences on other machines, generally installing twice, and am now getting rather frustrated.

Installing software shout not take 40 minutes unless you are installing an OS… installing software should not have to be performed 5 times (maybe more!) before an acceptable result is achieved.

What the hell, Adobe???