You shouldnt have to build a new server but you will need to upgrade each client (but not re-register, re-encrypt or anything). You can get further info on the upgrade process from the 7.0.5 documentation.

Otherwise, what setup do you have at the moment? no. of management servers, platforms etc?

David

if you've 703 server then upgrade it to 705 ---- if you build a complete new see 705 server and then try updating the client machines that have 703 from the last server and then these machines will not check in.... fresh deployment of 705 on client machines will work fine.

to keep it neat and clean I'll say upgrade the 703 server to 705 server -- create client packages and deploy them on the client machines.... go through docs -- they've explained well there.

thank you

Recalling the steps from documentation, if your upgrading from a version prior 7.0 it seemed to be a lot more challenging.  But upgrading from 7.0.4 to 7.0.5 was pretty easy.  Straight forward and quick.  I'm sure it'll be the same for you with 7.0.3.

I upgraded some clients to 7.0.5 and that too was seemless....they are checking in with no issues.

The one issue I did have (not related to the upgrade)...and this may come in handy to other newbies, is to schedule regular backups of the database!  Or convert it to a "simple" recovery model.  My clients weren't checking in and I found the transaction log was full.  I'm a real newbie in SQL...I took a class on it, but it was a basic database class and I never managed an SQL server before.  Not to mention, I didn't recall this being mentioned in the server installer documentation.

I am not a DB admin but for this either you can ask your DB admin to go for the SEE backup (as for any other DB) or you can increase the DB size of the ldf file to unlimited >>> this way you can manually take backup -- when you have time.