LANDesk 9.0 Update and Important Information.

The LANDesk upgrade is going smoothly so far. At this point, the new LANDesk servers are in place, and operational. All workstations that already had an agent on them are now in the process of reporting to the new server.


These workstations agents are still on version 8.8, so, I’m working on pushing updated agents to them to bring them to version 9.0.

Agents:

I have updated all of the agents out there on http://setup/ and http://landesk/agent to reflect all the new agents.

When you go to the setup page, you will notice that there are a few more options that I added for the agents:

LANDesk Windows Agent and Antivirus: this is the agent that everyone used to install on the workstations

LANDesk Windows Advance Agent and Antivirus: This agent is a little bit like a LANDesk agent seed (similar to Deepfreeze), it’s only about 1.5 Mb (as opposed to 86Mb), this is a very fast install on the client, and will allow the client to pull the agent down from the core server automatically, and install it. If you’re not in a hurry, or don’t care to monitor the process, using the advance agent on the client is a good way to go.

LANDesk Windows Agent and Antivirus (Windows 2000): This agent has a slightly lighter configuration for Windows 2000 machines, which are assumed to be running on less capable hardware. Please install this agent on Windows 2000 workstations.

LANDesk Windows Advance Agent and Antivirus (Windows 2000): This Advance Agent is like the one above with the only different that installs the agent with the lighter configuration for Windows 2000 machines.

Note that all these agents are configured with RealTime scanning Antivirus. The non Windows 2000 agents, are also configured for real time scanning for Malware, and Spyware.

The last 2 agents I created on the Setup page should be used only in special circumstances. They are the full blown LANDesk agent, but do not install the Antivirus engine. An “Advance Agent” version of this agent is also available.

Scheduled Tasks, Packages, Managed Scripts and OSD:

You will notice that the pre-existing package that used to be on the old server are no longer in the new one. This is because we create a new database, and I am working on re-creating those, as it will give me a chance to get a bit more organized in creating those tasks and packages. The packages themselves have all been preserved, the only part that needs to be re-configured is the joining of the package with the delivery method and the scheduled task.

If there are any Scheduled tasks that were on the old server that you use on a regular basis, please let me know, and I’ll recreate those ones first.

The new LANDesk Console:

With the new server, there is a new LANDesk console, and a whole new permission scheme that the new version uses. This version actually allows more granular control of user privileges, which may work to our advantage in giving you access that used to not be possible prior to today. Also, giving access to users in LANDesk can now be controlled from Active Directory, instead of the local security group on the core server.

In order to start using the console, you need to upgrade your existing console. Please note that you need to have the latest version of the .NET Framework 3.5 SP1. In case your setup doesn’t pass the pre-requisites, you can download it from the link above. Otherwise, follow these instructions to install the new console:

1. Go to file://do-ld-core/ldinstall$ and click on Autorun.exe

2. Click on “Remote Console” then click “Continue”

3. Once the pre-requisites are passed, click on “Continue”

4. Click “Ok”, “Next”, accept the EULA, then Click “Next”

5. The server name should be “do-ld-core”, click “Next”, then “Install”

6. If the installation was successful you will get green checkmarks to confirm the success. Go ahead and Reboot your machine, and your console should be ready for your use.

In order to login to the Console, you will see an option for Local Group or Active Directory. you need to choose Active Directory, and login with your credentials, the same way you did on the previous version: cvusd\username and your password.

Again, please remember to recreate any queries that you have, and/or be patient with me as I recreate all the public packages, queries and scripts for your use. This will take a bit of time, but I will get it all done.

We will still be working on additional things in the setup of the server through Friday, and may have to power down the server for a short of period of time, but for the most part, LANDesk should be available, and the agents can be deployed like usual.

I am working on a way to deploy the agents via a couple of different methods. I will keep you posted once I have a plan in place regarding that.

Thanks for taking the time to read through this long post.