The avalanche MDM is installed on Windows Server environment which is generally administered by a separate Windows team in large enterprises.
There are regular updates and patches applied to Windows server and as Avalanche application owners on the servers we are tasked with making sure the Avalanche environment is "healthy" after these patching.
I have documented below a cheat sheet of what needs to be checked after the patching schedule to make sure Avalanche is running as expected. These steps if documented can be performed by Support personnel and does not need an Avalanche expert.
Depending on the organisational setup modify the below with location of your files and installs.
1. Before the patching commences make sure there is a recent backup of the Avalanche DB.
2. Patching can commence.
3. After patching check that the Wavelink and Landesk services on the Enterprise as well as Device server are Started.
4. In the Avalanche console under inventory check that the devices are checking in with last contact time to be very recent.
In Avalanche 6 this can be checked in the Inventory tab.
Click on the last contact column heading to sort out in Descending order.
5. I also recommend having a test device connected to the environment before the patching. After patching of the server, from Enabler on the device perform a software update and ensure the device successfully connects to Avalanche.
6. Another test I would also recommend to do is have a Test profile in Avalanche always available and call it Server Patching. This profile can have one test package with a simple text file to be deployed to \Temp folder on the device.
After server patching deploy the package to the test device we had connected at Step 5. Check the device receives the text file in the \Temp folder.
There are regular updates and patches applied to Windows server and as Avalanche application owners on the servers we are tasked with making sure the Avalanche environment is "healthy" after these patching.
I have documented below a cheat sheet of what needs to be checked after the patching schedule to make sure Avalanche is running as expected. These steps if documented can be performed by Support personnel and does not need an Avalanche expert.
Depending on the organisational setup modify the below with location of your files and installs.
1. Before the patching commences make sure there is a recent backup of the Avalanche DB.
2. Patching can commence.
3. After patching check that the Wavelink and Landesk services on the Enterprise as well as Device server are Started.
4. In the Avalanche console under inventory check that the devices are checking in with last contact time to be very recent.
In Avalanche 6 this can be checked in the Inventory tab.
Click on the last contact column heading to sort out in Descending order.
5. I also recommend having a test device connected to the environment before the patching. After patching of the server, from Enabler on the device perform a software update and ensure the device successfully connects to Avalanche.
6. Another test I would also recommend to do is have a Test profile in Avalanche always available and call it Server Patching. This profile can have one test package with a simple text file to be deployed to \Temp folder on the device.
After server patching deploy the package to the test device we had connected at Step 5. Check the device receives the text file in the \Temp folder.
No comments:
Post a Comment