PAXTON Net2 SERVER MOVE

[Koldov]

A very, very long time ago Paxton was installed on to an Admin PC in the office. It hasn't caused any issues for years but recently we have had EntrySign installed and linked to Paxton.

 

This means that until the Admin computer is turned on (or possibly logged in to) in the morning then EntrySign can't communicate with Paxton, quite soon we will be getting everyone to use EntrySign and it will also open the door so it needs to be running 24/7 (whereas Paxton can open and lock doors even when the PC isn't running).

 

I can't remember the reason Paxton wasn't installed on the server, probably a combination of not wanting extra software on the server and the fact that it was being run by the Admin dept. in Reception and any changes to door times, personnel list would mean they would have to log on to the server to change.

 

If I've got that wrong, please enlighten me...

 

Anyway, move Paxton Net2 from PC to Server as is... any chance? Or is it complete uninstall/reinstall, new database, reinput all users, new firewall rules etc.

Edited September 19, 2023 by Koldov

[andy_b]

You can install Paxton on the server and then install the client on the admin PC so they can make changes etc.. as required.

 

Moving the install is usually as simple as backing up the database with the Net2 Config utility and then restoring it on the server.

[mrbios]

Paxton's nice and easy to move. Take a backup of the database in net2 configuration utility, shut it down. Install fresh on a new server, restore the database backup to that machine, job done essentially. The database knows the IPs/details of the doors, so it should pick those up, it brings all the users over in the database and so on.

 

You can install just the client back on the admin PC and tell it to connect to the server so they can still manage it.

 

Only thing i had to do when i moved ours, as we pay for the pro license, was give them a ring because the online activation wouldn't work, but they sorted out the license activation very quickly for me.

 

Alternatively you could just run a P2V move of the admin PCs setup to a server VM, but that's not as nice and tidy.

[howartp]

As above, nice and easy. Did it this summer.

 

If you have IO boards (input/output relay boxes) you need to untick them in the old server before you move, then tick them (and possibly talk nicely to them) in the new server to get them to re-talk to it.

 

(I had to tick DHCP, save, untick DHCP, save, on each board to get them to wake up - doubt that's the official solution but it worked!)

[Koldov]

Well, it might have just gotten a bit more complicated anyway!

 

I presume whoever installed the whole set-up for us used an 'installer' copy of the software.... and didn't leave us with a copy!

[howartp]

Install the lite version then restore the DB - the registration comes with the restore.

[pacapps]

I had this when I moved net2 from an admin PC onto a server.

 

If you get in touch with Paxton support whey will (they did for me any way) send a download link to get the software.

 

I also had to get something else sorted (cant remember what it was now) but they were very helpful.

[howartp]

http://www.paxton.info/1438

 

That's a permanent link to the latest version of Paxton; they give it out to anyone who asks so I don't know why it's such a secret.

[andy_b]

http://www.paxton.info/1438

 

That's a permanent link to the latest version of Paxton; they give it out to anyone who asks so I don't know why it's such a secret.

 

I just wish they had the changes listed like they used to. There is a whole difference between an update that has firmware changes and one that doesn't.

 

 

So - if you are moving to a newer version it is worth bearing in mind that the firmware updates will cause the doors to lock out, so schdule the move appropriately.

[Koldov]

Thanks all!

 

I did have a nice chat with Paxton support and they gave me a link for the version we are currently on (better the devil you know)...

 

One last question (ha ha ha I very much doubt that), there's two folders 'INSTALL' and 'OEM' both have set-up files in them, I'm presuming just the 'INSTALL' folder.... probably obvious, but I don't want to mess it up!

[Ex-MGSTech]

You make a backup in the config utility, not copy the folder...

 

Steve

[Koldov]

Well, it will not install on my server (2019)!

 

Unhelpful...

 

0x84c5c74b - Unspecified error

 

Then when I tried to reinstall it said it was already installed and gave a 'repair' option.

 

That failed with...

 

0x80070643 - Fatal error during installation

 

Is it half-term yet?

 

Time to go home...

 

[Koldov]

Great!

 

So, I just had a chat with Paxton support and...

"...this code 0x84c5c74b doesnt actually come up in our knowledge base - it's not one we see commonly. But I googled it to find its related to SQL"

 

I just wondered when I look through the install log it seems to reference installing SQL 2008, SQL 2012 and SQL 2014... is that right?

 

As they stated they are not SQL experts and can't advise on it as such, only the Net2 software itself, so the only other advice was:

 

"First try installing SQL separately from the included redist folder before trying Net2 again.

If this still fails, uninstall Net2 and all SQL entries on the PC after checking nothing else is using SQL and try to reinstall Net2.

If neither of the above steps work, they will need to install Net2 on a different computer."

 

and the classic....

 

"reinstalling windows is known to resolve this."

 

Unfortunately this is a big old server with many years on it (as it used to be the 'one' server) and many SQL instances already running or not being used anymore and having the OS been in-place upgraded a few times. I'm a bit wary of anything that will interrupt uptime as it's a prod server. It's also an ex-SIMS server with the install being kept in stasis for as long as I can until I am 100% sure we will never need it again (SIMS moved to a VM over the summer). It also runs a few other critical bits (Redstor, File Shares, HyperV).

 

I guess it could also be FSRM, SRP, Applocker or Sophos...

[andy_b]

Would it not be possible to install on a clean VM?

 

Multiple SQL version over the years looks to be causing havoc.

[speakercon]

Some of the older net2 versions are not supported on newer server OS's.

 

You could either try installing your older version on an older server OS or install the latest net2 version.

 

I've moved databases from much older net2 versions to the latest without any issues in the past.

[Koldov]

Would it not be possible to install on a clean VM?

 

Multiple SQL version over the years looks to be causing havoc.

 

Yes, could be the issue... I do have other VMs, but license wise (and host resource wise) I can't really justify having a VM spun up just to run Net2. I could possibly put it on one of the VMs I already have, but the purist in me likes the fact they are all split out for their own various roles and are quite slim. From what I saw of the Net2 software install it has quite a lot of 'stuff'. Adding SQL to these is just adding another load of updates and security holes to have to manage...

 

Some of the older net2 versions are not supported on newer server OS's.

 

You could either try installing your older version on an older server OS or install the latest net2 version.

 

I've moved databases from much older net2 versions to the latest without any issues in the past.

 

I had checked previously (and the Paxton support checked) that the version we are on is supported on the Server OS, I think the only issue (mentioned in a post above) was the newer versions need to pass updated firmware to the controllers and that it could even cause issues (one or two threads on here about it).

 

EDIT: I can't tell you how off I am with SLT for dropping this in at the beginning of term! Like I don't have enough to deal with already day to day! This is a job for the holidays, so we can test/troubleshoot and iron out all the kinks when nobody else is here...

Edited September 20, 2023 by Koldov

[Koldov]

I'm always wary of answers that say 'it's easy, just do this'.... I should know by now, that for some reason it rarely is...

 

Well, after a bit of a battle, a roll back, a reinstall and a restart (annoying as it meant I had to remote in last night after everyone had gone home and then wait until all the backups had finished to do it... ) I finally got it installed on another server...

 

I also had to get something else sorted (cant remember what it was now) but they were very helpful.

 

Was it this bit?

 

"Changing the Net2 PC

Site specific Net2 Files

All of the files containing the site-specific information in a Net2 system are stored in a single folder. This contains all user and door details, events, reports, pictures and back-ups. The default folder for this information is C:\Net2 Access Control. When changing PC it is important to copy the files contained within this folder across."

 

That is from the official Paxton instructions (I can't find anything newer. Although it says it's for V4 onwards, is it out of date?):

 

https://www.paxton-access.com/wp-content/uploads/2019/03/AN1071.pdf

 

I can't see that anybody has mentioned it, so it's either 'oh yeah, I forgot to mention that bit' or 'it really doesn't matter/it's not important/it works anyway/we didn't need that in our environment'...?

[andy_b]

The backup / restore should move everything. I have never copied this folder over.

 

Is everything in Net2 as expected?

[Koldov]

The backup / restore should move everything. I have never copied this folder over.

 

Is everything in Net2 as expected?

 

I haven't done the move yet, I think it's probably wise to wait until most people have gone home.

 

Oh... now I'm even more confused!

 

The procedure in the instructions I linked, doesn't appear to be a 'backup' of the whole Net2 system as such, it just seems to say that it is copying the 'database' which you can restore to the new computer.

 

"Using the Net2 Server Configuration Utility, go to the Database tab and click the Create Copy button. This creates a copy of this existing database into a Zip file."

 

Maybe there's a terminology mix-up somewhere, or you know of a different procedure for doing a backup to include all the other relevant files?

[andy_b]

What version of Net2 are you using, I have (in recent memory) only ever done the below procedure.

 

Old system:

Take a backup using configuration tool.

 

New system:

Install Net2.

Use configuration tool to restore backup.

 

Nothing else, the database contains everything.

[Koldov]

We are on V6 point something, point something, point something...

 

This is what I'm looking at:

 

Edited September 21, 2023 by Koldov

[andy_b]

Create Copy on the old install.

 

Import Copy on the new install.

[mullet_man]

Does anyone have a copy of an older installer?  V5?

 

I've had to re-image my PC and our building owners are still running the older version and the V6 one doesn't work.

[ovenchips]

I've contacted Paxton directly in the past and they've been fairly helpful at giving out download links to older versions, if that helps at all.

[mullet_man]

3 hours ago, mullet_man said:

Does anyone have a copy of an older installer?  V5?

 

I've had to re-image my PC and our building owners are still running the older version and the V6 one doesn't work.

Thank you to the people who have reached out to me.

 

Really appreciate it 👍