Bacula v5.0.2 Windows Installation Issues

Traversing Windows 2008's (and Vista's, and Windows 7's) backwards-compatibility links doesn't really work as expected. Why is a question for MS.

Each of the examples in the block you provided requires these links:

Could not open directory "C:/Users/Administrator/My Documents/My Videos": ERR=Access is denied.

Should be C:/Users/Administrator/Videos

Could not open directory "C:/Documents and Settings/Default/Application Data": ERR=Access is denied.

Should be C:/Users/Default/AppData

Note that many apps that used this path now use the C:/ProgramData/ directory (which used to be C:/Documents and Settings/All Users/Application Data).

Could not open directory "C:/Documents and Settings/Administrator/AppData/Local/Temporary Internet Files": ERR=Access is denied.

Should be C:/Users/Administrator/AppData/Local/Microsoft/Windows/Temporary Internet Files

It's a pain, but Bacula should work just fine in Windows 2008 as long as the paths are set to the new style.

Update: The original question was for Windows Server 2008, but the solution is easier for Windows Server 2008 R2 and Windows Server 2012 (and Windows 7 and 8). You can add the user through the NTFS UI by typing it in directly. The name is in the format of IIS APPPOOL\{app pool name}. For example: IIS APPPOOL\DefaultAppPool.

IIS APPPOOL\{app pool name}

Note: Per comments below, there are two things to be aware of:

• Enter the string directly into the "Select User or Group" and not in the search field.
• In a domain environment you need to set the Location to your local computer first.

Reference to Microsoft Docs article: Application Pool Identities > Securing Resources

Original response: (for Windows Server 2008) This is a great feature, but as you mentioned it's not fully implemented yet. You can add the app pool identity from the command prompt with something like icacls, then you can manage it from the GUI. For example, run something like this from the command prompt:

icacls c:\inetpub\wwwroot /grant "IIS APPPOOL\DefaultAppPool":(OI)(CI)(RX)

Then, in Windows Explorer, go to the wwwroot folder and edit the security permissions. You will see what looks like a group (the group icon) called DefaultAppPool. You can now edit the permissions.

However, you don't need to use this at all. It's a bonus that you can use if you want. You can use the old way of creating a custom user per app pool and assigning the custom user to disk. That has full UI support.

This SID injection method is nice because it allows you to use a single user but fully isolate each site from each other without having to create unique users for each app pool. Pretty impressive, and it will be even better with UI support.

Note: If you are unable to find the application pool user, check to see if the Windows service called Application Host Helper Service is running. It's the service that maps application pool users to Windows accounts.