HP Device Manager 5.0 Migrating & Upgrading HPDM 4.7 to HPDM 5.0 | HP Computers | HP


Welcome to HP Device Manager 5.0, Migrating and Upgrading HP Device Manager 4.7 Tutorial. As a disclaimer, this tutorial makes the following assumptions: That a legacy Windows Server (2003/2008) is setup, configured, and introduced into your environment. And that HPDM 4.7 is setup and configured
on the legacy Windows Server. And that finally, a new Windows Server (2012/2016) is setup, configured, and introduced into your environment. As part of the tutorial we will be covering
the following: Downloading HP Device Manager 5.0 executable on both Legacy and new Windows Server. Executing the HP Device Manager 5.0 executable on Legacy Windows Server. Reviewing Complete Setup and/or Destination Folder on Legacy Windows Server. Reviewing Pop-Up Dialog Indicating Uninstall and Backup on HPDM 4.7 Legacy Windows Server. Collecting Legacy Windows Server HPDM 4.7 Backup at the following directory. Collecting Legacy Windows Server HPDM 4.7 Master Repository at the following directory. Moving the Legacy Windows Server HPDM 4.7 backup and Repository to the New Windows Server. Creating the Restore Registry Edit File on
New Windows Server. Executing HP Device Manager 5.0 executable on New Windows Server. Reviewing Complete Setup and/or Destination Folder on New Windows Server. Restoring Legacy HPDM 4.7 Windows Server Backup on New Windows Server. Checking Preconditions and/or Mitigating on New Windows Server. Allowing all seven Components to Install and reviewing the Admin Guide on the New Windows Server. Launching HPDM 5.0 Console on the New Windows Server. And then finally confirming the Restore on
New Windows Server. As a couple of notes: If Microsoft SQL server is being used, re-configuration of the logon account and password will be
necessary. And also, when moving the master repository to the new server, re-configuration of the repository settings will be necessary. Let’s begin! Starting with the Legacy Server environment, I have already downloaded HPDM 5.0 executable and placed that on my desktop. There are three steps that we need to complete on our Legacy server environment which happens to be running Windows Server 2008 R2 Standard. Keep in mind that in order to be compliant
for HP device Manager 5.0 your environment must be server 2012 or higher. For step one, we are going to go ahead and
execute our HPDM 5.0 executable on our desktop by double clicking on the shortcut. We will then click run at the UAC. And now we’ll confirm the save file location. This is the default location at c:/swsetup/HPdevicemanager5.0. If we wish to change that, we can go ahead
and click change. For now, we are going to go ahead and click next, and it will then extract the files to that location. Once the extraction is complete, we will get
greeted with the popup saying that setup cannot continue because the following software installations were detected. It will list HP Device Manger 4.7 and the
respective service pack that you have installed. In this case, it’s Service Pack 12. It will also list HP Device Manager Embedded HTTPS server, and then it will go on to explain the software configuration and management database have been archived and will be safely restored during the installation of HP Device Manager 5.0. Please uninstall the software components identified above from the system before continuing with this installation. We are going to go ahead and click, OK. And now, as part of step two, we are going
to go ahead and click on the file explorer icon here in the taskbar. And then click on computer. And then double click on the C-drive. The backup that popup identified is placed
at SW Setup underneath the C-drive. I’m going to go ahead and right click it,
choose copy, and paste this to my desktop. You have the option of pasting this wherever it is necessary. I am then going to collect in the same way
the Inetpub directory. If you are familiar with HP Device Manager
4.7, Inetpub directory is where it places the contents of the master repository. So I’m going to go ahead and right click
that, choose copy, and place this to my desktop. Now, that we have collected both the backup and the master repository contents, that will complete step two of the process. And now we will move onto step three. Which is we’re going to migrate these two
files into our new server environment. This is our new server environment running
Server Standard 2016. I’ve went ahead and placed those two files on the desktop. I’ve also downloaded a copy of HP Device
Manager 5.0 executable and placed it on the desktop. And I have also added a restore registry file
to the desktop. The contents of this registry file are in
the admin guide. And just to show you contents, I’m going
to right click it and choose edit. And you will notice that it is simply changing and adding a registry entry for allowing us to restore the backup that we collected from our legacy environment. The new install will also include three steps. We will begin by copying both of our files
from our legacy environment into the same identical locations on this new server. I’m going to go ahead and click on the file
explorer in the task bar. And then This PC. And then double click on the C-drive. Then I’m going to go ahead and highlight
both files and drag them into the C-drive. Now that they are sitting on the C-drive as
a secondary step, I will go ahead and double click on the restore registry file. I will then get a popup saying adding information can unintentionally change or delete values and cause components to stop working correctly. If you do not trust this source of information, listing out our file, do not add it to the registry. Are you sure you want to continue? We are going to go ahead and click yes. And then we are going to get another popup that says the keys and values contained in that file have been successfully added to
the registry. And now we are going to click okay. That completes step two. Now as the final step, for step three, we
are going to go ahead and launch the HP Device Manager 5.0 executable. I’m going to go ahead and double click on
the shortcut. And now I’m going to go ahead and click
Run at the UAC. It’s going to point out the save file folder
location. Just as before, it is C:/SWSetup/HPDeviceManager5.0. If I wanted to change that, I could go ahead
and click change. I’m going to go ahead and click next. And wait for it to extract the file contents. Once the extraction is complete, I’m going to get a popup that says, this software configuration and management database of a previous installation have been detected. Click restore to safely restore the data during the installation of HP Device Manager 5.0 or click skip to perform a clean installation. Since we are using our backup, we are going to go ahead and click restore. And now, we are going to get greeted with
the Welcome to Install wizard for HP Device Manager 5.0. And we are going to click next. As part of step one, we are going to review
the License Agreement from top to bottom. Once we’ve reviewed the License Agreement from top to bottom, we are going to go ahead and click the check box for I accept the terms of the License Agreement. And click next. For step two, we are going to select our setup type. For the purposes of this tutorial, we are
going to go with the complete installation. But just to show you the seven individual
components, I’m going to bubble in custom. And then click next. This will show you the individual seven components of HP Device Manager 5.0, their installation size, and their packaged versions. I’m going to go ahead and click back. Bubble in complete. And now verify the destination folder for
where I want those seven components to be. If I wished to change them, I will go ahead
and click browse. For now, I’m going to go ahead and click
next. For step three, it’s going to check the
preconditions. I’m going to go ahead and click, Check. It will list all individual ports necessary
for HP Device Manager 5.0 to function. And as I scroll down to the very bottom, it
will also list the precondition for space for each of those seven components. You should see green check marks from top to bottom. If you see red marks. This will be your opportunity to mitigate
or reconcile where necessary. Once you see green check marks from top to bottom, you will go ahead and click install. And move onto step four, which is installing
these seven components. I’m going to go ahead and click install. While it’s installing the individual seven
components, we are going to go and review the Admin Guide. Starting with page 12, which is the installation. We are going to review the individual components. All seven of HP Device Manager 5.0. Beginning on page 12 it’s going to be begin
listing those seven components. And it’s going to list the individual requirements. Noting here, that once again, you must have Server 2012 or newer to install HP Device Manager 5.0. It will also list out the respective memory
sizes and disk spaces. Please take into consideration what you hope to accomplish with HP Device Manager 5.0 and the individual file save sizes that you are needing for your payloads. Scrolling past page 12 onto page 15, or excuse me, 14, where it ends. You will notice the Product Support Matrix
where it will list the individual Thin clients that are supported for HP Manager Device 5.0. Scrolling past page 14, on page 15, it will
list the Windows Firewall Settings. The general ports that HP Manager 5.0 require to be running is the range of ports 40,000 to 40,009, and also, ports 40,012. There are additional ports necessary for HPDM to function properly. Those will be identified further down in this
Admin Guide. Scrolling past page 15, now looking on page 16. It’s going to list out the individual commands for your advanced firewall that you need to use to open up those individual ports. Scrolling past page 16 and onto page 17. It’s going to identify the individual setups. In prior tutorials we took you through the
complete setup on page 17. And also, the upgrading an existing installation on page 22. This particular tutorial will be covering
Migrating HP Device Manager 4.7 data to a new machine and upgrading. Scrolling past page 23 will outline the steps
that we are covering today in this tutorial as well as some snapshots. It will also show you the registry keys that
I used or will be using. Scrolling past all the way to page 29. It’s going to list two topologies. The top topology will be a standard topology. The bottom topology will be a more advance topology. Starting with the topology up at the top,
all seven components are going to be installed on the same piece of hardware or virtual machine. And looking at the bottom, all individual
components will be broken out into individual pieces of hardware or virtual machines. Utilizing the lower topology, I’m going
to go ahead and explain the flow of how a deployment request will work. An admin will use the web browser or the software console to create a deployment request. That deployment request will then get sent
to the HPDM server component. It will then use the database either Post
Crest or Microsoft SQL for its logical data. It will then request the payload from the
master repository component, and the child’s repository components if present. It will then use the HPDM gateway component to go ahead and send out that deployment request to your individual Thin clients. And now we are going to go ahead and check on our installation. As you notice here the installation was a
success. If we needed to reconfigure our Microsoft
SQL server, we would go ahead and check mark the launch HPDM Configuration Center checkbox and continue on there. Since we are using Post Crest for the default installation. I’m going to go ahead and click finish. And I’m going to give it a just few moments
to go ahead and complete the setup. If you notice here on the desktop there is
an HP Device Manager Console icon and shortcut. I’m going to go ahead and double click that
to go ahead and Launch HP Device Manager 5.0. And now, I’m going to use the login and
password from my prior environment. Once I’m logged in, it’s going to show
me the splash screen, and eventually drop me at the home dashboard. This is the home dashboard that will show
six individual tiles for the six individual features of HP Device Manager 5.0. Just to verify that our restore was successful, I’m going to go ahead and start with clicking Managing Devices tab. Looking at the individual OS drop down, you are going to notice the OS that match your environment. In my particular case, I have Win10IoT and
Thin Pro. As I click on each of these individual OS
and if I leave the group to the default Dynamic Group for the gateway and click on it. You will notice that it will list the individual
Thin Clients as part of that OS and group. In the same way, if I were to go ahead and
click on HP Thin Pro 7 and leave the default Dynamic Group and then click on the gateway. You will also notice the respective Thin Clients there as well. So, we know that it took effect properly. Now, to confirm our repository we are going to go ahead and check on Gateways & Repositories tab and click on that. Off to the side menu, we are going to go ahead and click on Repositories. If I left click on the Master Repository, it
will change blue. And now I can go in and right click, and choose
edit. From here, I will want to change the server
address to the new server address. And then I will need to take the opportunity
to click on Protocols, re-select my protocols if they weren’t restored, and then set the
individual settings for each protocol here. I will also want to go in and check on Users
& Groups. So, I’m going to go ahead and click on Users & Groups and confirm all my users are present. And all my groups are present by clicking
on the menu and verifying the groups. Since I didn’t add any additional groups
or users, I have the standard groups and standard user of root. As part of this tutorial, we demonstrated
the following: Backup of the Legacy Server and Restore and Upgrade of the New Server. I would also like to invite you to our webinars every Tuesday and Thursday at the following links. This concludes our tutorial.

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Post navigation

Leave a Reply

Your email address will not be published. Required fields are marked *