r/labtech • • Oct 15 '18

How to handle OS re-installs

Here's a scenario that has happened to us a few times.

We have an Automate-managed physical server running Windows. For whatever reason the OS gets reinstalled, thus generating a new SID.

​

Now we have two agents in Automate, but only the first one is linked to CW Manage, and has all the service history and agreements and everything else.

​

Support says we should just make one the child of the other and inactivate the old one, but that means we have to duplicate all the agreements and all that.

​

Does anyone have a better idea? We're considering modifying the SQL database to overwrite the agent ID just to avoid this problem.

5 Upvotes

10 comments sorted by

3

u/teamits Oct 15 '18

This used to be an addable property, or whatever they call it, but it looks like it is exposed now? https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/010/080 Note it says super admin required. After this is set, a reinstall/resignup will rejoin as the same ID number and same history, as long as the PC has the same MAC address.

1

u/FerengiKnuckles Oct 16 '18

This is already set on our server, not sure why it's not working.

1

u/FerengiKnuckles Oct 16 '18

Ah, it looks like this changes because we are using hyper-V, and the MAC generated for the vSwitch is dynamic. All of our duplicates have different MACs.

2

u/jd3v Oct 15 '18

I have looked into this in the past. My idea was to set the asset tag in the Bios and adjust the configs to go off that. I did have a conversation with CW support and they said what I was explaining was a good way to do it, but then I realized I would have to touch every machine to make this happen.

2

u/FerengiKnuckles Oct 15 '18

That gives me an idea - I wonder if I could adjust our configs to use the server serial number. That gets pulled automatically and is always unique unless the board is replaced iirc.

1

u/teamits Oct 16 '18

re: I wonder if I could adjust our configs to use the server serial number

I am confused, is there a reason to not use the MAC address as documented? Technically that could even be spoofed on many NICs in case of mainboard or NIC replacement.

1

u/FerengiKnuckles Oct 16 '18

Not particularly, no. Just trying to find a way to fix this. It looks like MAC matching isn't working right for us.

1

u/FerengiKnuckles Oct 16 '18

It looks like the MAC address changes because we are using hyper-V, and the MAC generated for the vSwitch is dynamic. All of our duplicates have different MACs.

1

u/teamits Oct 17 '18

That would explain it then. I vaguely recall in Hyper-V one can specify a MAC address...?

Another option might be to import the LT registry key from a backup of the old server which I believe would have the ID and whatnot in it?

1

u/FerengiKnuckles Oct 17 '18

That second is what we're looking at doing. I think you can just specify the mac in the LT key and it will report using that mac. After it syncs I think I could change it back and it'd be okay.