Hi. My name is Derek Aberle, and I'm a Quest Software technical support engineer. In this video, I'm going to demonstrate an upgrade of Desktop Authority to version 9. One of the requirements for upgrading to 9 is that you need to be on at least version 7.80 or above in order to run the upgrade. In this demonstration, I'm going to be upgrading version 8.12 to 9.
There are a few things to consider before upgrading to Desktop Authority version 9. We highly recommend installing Desktop Authority on a member server, not a domain controller. You can install it on a domain controller if that's your only option, but we recommend installing on a member server. This server should be a dedicated server and should have a minimum of a 2 gigahertz dual core CPU and at least 4 gigabytes of memory.
Desktop Authority 9 runs on IIS as a web application. The Desktop Authority installer will install IIS if it needs to, and it will also back up your current IIS configuration if you already have existing sites.
Another important thing to point out is that Windows 2000 is no longer supported in Desktop Authority 9, as well as SQL 2000 in Windows 2000 domains. Please review the install and upgrade guide for additional information regarding operating system requirements and any prerequisites that may need to be installed. Some of these prerequisites may require a reboot of the server.
OK. So now we're ready to run the installer. Click yes to the UAC prompt if it comes up. Next is to accept the license agreement. And then let the setup files extract. Some of the wait times will be cut out of this video to save some time.
Now here, this is letting us know that the original folders are going to be removed because the folder structure is different for version 9. So anything in those folders will be saved. So click Yes to continue here.
Here it's going to check to see if IIS is installed. If it's not, just click the button to install it. And then after that, we'll click the button to install the prerequisite packages. And then when this is done, we'll click the button to start the required services on the server. And then we'll click Next.
Here it's going to pick up the existing SQL server in instance, so we'll just click Next. Here is where you would change the install path if you want to install it to a different folder. And by default, the installer will make backups of the existing databases. If you don't want to make backups, just uncheck the bottom two boxes.
Next we're going to enter a domain admin account for the two services. The Operation Service, formerly known as the Ops Master Service. And the Desktop Authority Manager Service is new to version 9. This service does require an admin account. And then click Next.
Here's the super user group. By default, it's domain admins. Next we're going to give a user account for the IIS application pool. This can be any account. Doesn't have to be an admin account. Can be a user account.
And then we're going to pick the website to install to. By default, it'll go to the default website. If you've created your own site, you can pick that other site.
And then on the next screen, we're going to use a self-signed certificate. If you already have your own certificate, by all means, you can use your own. If you don't have one, then the installer will create a self-signed certificate.
On the next screen, we're going to click install and let the setup process run. Again, some of the wait times have been cut out of this video for the interest of time.
Next, when we go to log in to the console, you can check the box to use your current Windows credentials. You're going to notice another Windows credentials box comes up. To get around that, just go into your browser. Go to Internet Options, Security tab. And we're going to add this site to the local intranet zone. This does require a browser restart. And when the browser restarts, you will not see the Windows credentials box come up.
So now we're into the Manager. And the first thing that we should do is go to Server Manager, which is in Deployment Settings. And we need to let any servers that are in the list query for the status of the services.
And the services are going to be out of date. So we just right-click anywhere on the line. Go to Administrative Service, and then click Update Image. That will update the Administrative Service, which is formerly known as the Script Logic Service.
And then the Update Service may or may not be installed. If it is installed, just go ahead and right-click. Go to Update Service and, again, Update Image. And that will upgrade the Update Service. And when it's finished, both services should show with the green status.
Next, we're going to go just verify the data in some of the profiles. In this example, there's only one profile. So I want to check and make sure that my elements are still there and everything looks correct.
Once everything looks correct and you're happy, update the client files, Yes to confirm, and then Replicate. Again, click Yes to confirm. And close the Replication window.
It's not a bad idea to go back to Deployment Options, or Deployment Settings, rather, in Server Manager. And just verify that everything is green all the way across the board. And you may have to click on the Refresh button in order to refresh the Server Manager page. And everything's green. Should be good to go to have the users start logging out and logging in to get the updated client on the workstations.
For more information about Desktop Authority, visit quest.com/desktop-authority. Or for product
07:16
