How will I migrate EM library to my newly installed SUM?
This thread was automatically locked due to age.
Hi,
you've already written about a failed migration on Friday. Is this just a reminder or a new question? Don't be (excuse me for repeating myself) parsimonious with details. Please describe your setup (especially where EM Library and SEC are installed) and the steps you have taken during the migration attempt.
Christian
OK I will explain.
Right now we have Sophos Enterprise Console (SEC) 3.1 and Enterprise Library 1.3.3. I'm planning to upgrade it to SEC 4.0 and Update Manager. Our current installation of this software resides on drive D:\ and thus, I would want also to install SEC and Update Manager to drive D:\, but every time I finished the installation of the whole software (I just followed the documentations and procedures that are available on Sophos websites) I always end up getting the error that my migration to the Update Manager failed. (I did this whole thing on my test servers with the same setup and configurations as with our existing environment as discussed).
Every time that I encounter this problem I just re-do again the whole procedure and I'm just wondering how come sometimes I was able to get the migration to the Update Manager correctly?
Ok my second question is, after I have already migrated the workstations to the update manager I always received this kind of a warning " EM Library is still running in the updating hierarchy. It is recommended that you migrate all your updating settings to Sophos Update Manager." I already checked the report and it seems like everything has been migrated successfully. How can I disable the EM Library from the updating hierarchy?
I'll try the second one:
How can I disable the EM Library
Just open the Manage Libraries link from tools (or the EM Library last updated under Updates on the dashbaord). This should give you a prompt asking whether to remove EM Library and related stuff from the console. Afterwards uninstall EM Library.
Can't say a much about the other issue without details from the report.
Christian
I'll answer you last question first. The Updating Hierarchy report may have additional pages you aren't seeing. Try clicking for the next page until the '+' next the page number is gone. There is a stored procedure that has to be triggered to get the option to clear the EM Library information from the Console. The pre-requisite is that all Groups be moved over to updating policies that are managed by SUM. The group does not have to have any computers in it, and it will still require that it be switched over to the SUM update locations. Once this is done, you should get a notification that you are no longer using any of the EM Library maintained update locations and would you like to remove the EM Library references or manage your EM Libraries. Answering Yes to this dialogue will open your EM Library, answering No will remove the EM Library references. (I know, it sounds backwards, but if you do like I did the first time and read it too fast you'll click on the wrong option)
As to your first question, assuming your migration ALWAYS fails, this may be due to configurations in your EM Library. Some of the requirements for the migration to complete are that your EM Library is pointed to Sophos, that no custom schedules are in place, and that the software package you are downloading matches your license. This last one is a common sticking point. Lets say you purchased the End Point Security & Control license, but subscribed to the Sophos Anti-Virus for Windows package in your EM Library. This package is an Anti-Virus only package and you are licensed for both the Anti-Virus, plus the Firewall and NAC with your license type. When your EM Library is migrated, SUM tries to find the Anti-Virus only package in the warehouse using your license information. Due to changes in the backend, only the ES&C package is available, not the AV only package. This will cause a migration failure.
The other common issue with migration failures is that Sophos is set for both the primary and secondary update sources in EM Library. This will also cause a migration failure, and simply setting EM Library back to only needing the primary is not sufficient to correct this. You have to first get the secondary update server information to be blank, then set it so the secondary is not in use. You may have to do this a couple of times before the change will stick.
Correcting your software subscription in EM Library to match your license type or correcting the secondary update server config will allow a successful migration if those were the issues you were facing. If not, we'd need to see your migration report, migrationdata.xml, and emlexp.xml information to understand better.
Just wondering about disabling the EM Library...
What I did before on my test is that I transfered all of my existing computer groups to SUM then I verified the legacy policy by viewing the groups that are using the policy. No computer/computer groups is using the legacy policy. I also checked the hierarchy report and verified that no groups are using the legacy policy. Then I closed and open again the enterprise console and thus it prompt me to remove the old em library from the updating hierarchy.
How come now on my installation itself the notification to remove the em library doesn't prompt me? I just did the same procedure that I did during my test but to no avail it still didn't prompt me to remove the em library?
Did you click Tools->Manage Libraries? That's where you get the prompt about removing EM Library. At start it's always the still running.
Just asking - I knew I'd seen seen the prompt (but still have EM around for testing). So seeing your question I stopped using the last legacy policy and was surprised that I got the still running. Took me three report views and four console open to find out that you have to go through Tools ...
Christian
Is it possible to remove the 'em library is still running in the updating hierarchy' when the EM Library is no longer installed on any of our servers?
We had Em Library running on our SBS box, and when doing the update to Enterprise Console 4.5 and Update Manager, it was installed to a new server as Sophos recommended not installing on the same box.
All machines are now using the new policies, all are updating correctly and reporting correctly through Enterprise Console 4.5
No machine is still using a Legacy Updating Policy.
And Sophos has been removed from the main server, but we still get this error message.
On the last page of the Updating Hierachy Report, it lists the old server as the EM Library Server, but no policy is listed that uses that CID
Below that it lists Groups using Legacy updating policies
It lists Default (which I presume is a policy name as we have no groups called default). and the number of groups using this policy is 0.
But we still get that error message.
It is not possible to go the Enterprise Manager, Tools, Library and Remove that library... obviously this is a problem.. is there any way around this? or do we have to live with this thing complaining about the setup from this point forward?
Thanks
4.5 has it too if EM Library is still running - usually it prompts you whether you want to remove it once it assumes that EM is no longer used and then it is gone. If you get the prompt but don't have Tools->Manage libraries I think it is a bug and you should report it to Support. Is the old server listed under Update managers and if so, can you delete it?
Checking the Do not ask me again box will suppress the prompt (you can re-enable it like all prompts using Tools->Confirmation dialogs ...)
Christian
