Microsoft has released Service Pack 2 for Windows Server 2008 & Windows Vista. The reason I haven’t put this on my blog in much detail is because I don’t use either at present. Vista is terrible & I haven’t had time to migrate to 2008 Server yet.
Way to much other important stuff going on in my work life at present to warrant the upgrade to 2008 Server. I have already tested 2008 Server and find the changes trivial, I’ve also looked at Windows 7 it’s a vast improvement on Vista.
I don’t know who made these but they work, whoever you are I salute you. Since Canon are tools & wont make the drivers for the Canon LiDE 50 scanner for 64bit Windows, someone hacked them together from drivers of another (LiDE 60) Canon scanner.
Device support for this scanner is not included within Microsoft XP/Vista/Windows 7 x64 or provided as an installable driver by Canon. To resolve this lack of support please install the modified driver below.
This package is based on original Canon ScanGear driver for the LiDE 60 and includes the full ScanGear GUI TWAIN interface required to operate the scanner.
Modifications for the LiDE 50 include:
Insertion of Hardware ID
Insertion of Device ID
Replacement of LiDE 60 Colour Profile with correct LiDE 50 ICC file
Insertion of correct flatbed scan area dimensions and imaging capabilities
If you have not yet plugged the Scanner in then when you plug the scanner in Windows will ask you for the location of the drivers, however if you have already plugged in and cancelled this request then you will need to follow the next steps:
Open Device Manager.
Scroll through the list and look for other devices
Expand the other devices group, you will find a device with a yellow exclamation mark on it
Right click on the device
Click Browse my computer for driver software
Click on browse and then navigate to the folder you extract the files to on your Desktop (I.e. the extracted ZIP file) then click next (check Include subfolders if it is not selected)
If Windows thinks the driver in the folder is a match for the device you selected, it will install it.
Once the Wizard finishes successfully, Reboot to allow driver installation to complete
If the installation Wizard was not successful then this driver is not going to work, this usually means you are trying to install the wrong hardware or have a version of Windows that this does not work with.
OK so I got sick of McAfee SiteAdvisor the new layout of their site is horrible and not user friendly, the button in your browser interferes with the aesthetics of the browser. SO now I have replaced it with WOT.
WOT is a free Internet security addon for your browser. It will keep you safe from online scams, identity theft, spyware, spam, viruses and unreliable shopping sites. WOT warns you before you interact with a risky website. It’s easy and it’s free.
The best part about WOT is that it’s community driven and not rapped up in the interests of a company like McAfee.
You’re reasons for needing Moving Symantec Endpoint Protection Manager to another server are your own, but either way, here is how I did it.
Looking around the web you’d find that there 2 ways to getting around this.
1 Using Replication Method
2 Backup-Restore Method
Out of the two the replication method seemed to make more sense, and looked the easiest to get done.
In summary what we need to do is:
Install SEPM on a new server
Configure it for replication with the first site
Change the priorities of the management servers to reflect that this new server is of higher priority; or simply assigning all groups to
this new server.
Uninstalling old SEPM
Here is now you do that, step-by-step:
First install Symantec Endpoint Protection Manager on a new server
When you get to the Management Server Configuration Wizard panel, go through with the Advanced Configuration type; Select how many computers will be managed by this server
Choose to Install an additional site. This is the only option that will install a Management Server and a database for replication.
In the Server Information panel, accept or change the default values and then click Next
In the Site Information panel, accept or change the name in the Site Name box and then click Next. The Site Name cannot be the same as what you have on your other SEPM.
In the Replication Information panel, type values in the following boxes: Replication Server Name (The Name or IP address of the old Symantec Endpoint Protection Manager) Replication Server Port (The default is 8443) Administrator Name (The Username used to log on to the old console) Password (The password used to log on to the old console.)
In the Certificate Warning dialog box, click Yes
In the Database Server Choice panel select either the Embedded database or the Microsoft SQL Server irrespective of what you have on your old server and click Next to complete the installation.
Log in to the new Symantec Endpoint Protection Manager (SEPM) and ensure that all the clients and
policies are Migrated successfully
Click Policy Components
Click Management Server Lists.
Select the Default Management Server List for ‘NEW SEPM’
Click Assign the List
Select all the locations, groups and click Assign to replace the existing Management Server list with the old server with the new one.
Wait for all the clients to reflect this change and connect to the new server. We can go through logs entries or on the SEPM Clients tab of the new server, you’d see the computer icon with a green dot for the ones connected to it, and a computer icon with a red arrow showing the clients still connected to the other server.After the successful Migration. I let this configuration run for a few days before the following
Uninstall the old Symantec Endpoint Protection Manager (SEPM)
Log in to the new SEPM and delete the old SEPM server from the Replication partners list and the Remote Sites
Under the Management Server Lists Policy Component, Delete the Default Management Server List for ‘OLD SEPM’
If you are interested in downloading a copy to play with and for application testing then head on over to the Microsoft site. This time it will be available until July so there is plenty of time, there is also no limit on the number of product keys either. The Windows 7 RC expires on the 1st June, 2010.
File information for Windows 7 Release Candidate 32bit: