Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 492
  • Last Modified:

switching from one server to another

We are going to be phasing out one of our servers and currently it hosts the Symantec Antivirus v9 and is hosting all signature updates. We have about 40 workstations that were set up with SAV v9.0 in a GPO and pushed down to them during the logon process.
I now have a new server set up with SAV v10.2 and I am wondering what the best way to make the 40 workstations point to the new server with the least amount of work. I really don't want to visit each workstation though.
Is it possible to push down a GRC.dat file to point to the new server? What are my options?
0
johnbowden
Asked:
johnbowden
  • 4
  • 4
  • 3
  • +1
1 Solution
 
bradl3yCommented:
Do the symantec AV clients look for the server by IP, or by DNS? If DNS, you can add an A record to your DNS server that points the old hostname to the new server.
0
 
michaelgoldsmithCommented:
Just do a push update to all of the clients to the new 10.2 client software using the Symantec console.
0
 
johnbowdenAuthor Commented:
I'm not sure. How could I find out?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
bradl3yCommented:
First I would find out how you would even go about updating a workstation to point to the new server. At some point while updating or installing a client, it should ask you to specify your Symantec AV server, whether or not you specify and IP address such as 192.168.1.100, or a hostname such as NortonAV.domain.com,  will determine whether this is possible.

From what you are saying, it sounds like the GRC.dat file contains the configuration for the clients? Is that a plaintext configuration file? Try opening it in notepad perhaps?
0
 
bradl3yCommented:
michaelgoldmsith's solution may be the best. I have not personally dealt with Symantec AV before, and did not know that was a possibility.
0
 
michaelgoldsmithCommented:
Sure. Use the console to discover the clients and push the new update out to them.
0
 
KutyiCommented:
In you Symantec 10.2 console make the new server a primary server.  Drag the PCs from one server to the other and wait until all your PCs have been turned on and given a chance to more over, a couple of days.  Then go around and check some randomly.
0
 
johnbowdenAuthor Commented:
Ok, that sounds good. Thanks for the sugestinons. What about the GPO that I have in place that points to the old server. Should I just disable it or delete it for that matter?
0
 
KutyiCommented:
I would remove it
0
 
johnbowdenAuthor Commented:
Just getting back to this issue, I have SAV loaded on both servers. On the primary server, it has all of the users. I've tried dragging the users over to the new server but they won't go over. Do I need to make the new SAV server the Primary Server first and then move the users?
0
 
KutyiCommented:
Yes
0
 
johnbowdenAuthor Commented:
So, here is the solution. I had to go to each workstation and run the setup file located on the new server so it would pull the signatures from the new server.

I spent about 2 hours on the phone with Symantec, they took control of the session and ran some programs that never did work. Symantec said that the issue was going from version 9 to version 10 and then over to a new server.

I wasn't happy that this was the only solution. It's done and all workstations are moved over to the new server

0
 
KutyiCommented:
Too bad, but it is done!  Don't forget to close the question.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

  • 4
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now