This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SEC Migration - All Windows endpoints have 'Awaiting policy transfer' now

Hi,

We recently built a second SEC instance (Windows 2019) to decommission the original SEC instance (Windows 2012R2).

The Windows instances are all connected and up to date, but they are in policy compliance state of 'Awaiting policy transfer'.

The firewall/networking hasn't changed and the old SEC instance is still running. TCP/8192 & 8194 are open on the SEC instances (inbound).

How should we proceed?

David

This thread was automatically locked due to age.

Parents

0 QC over 3 years ago

Hello David,

The Windows instances are all connected
to the new server? How have they been "moved" or directed to the new server?

Christian
Cancel
Vote Up 0 Vote Down

Cancel
0 David Lewis1 over 3 years ago in reply to QC

Hi QC,

We edited the Default Updating policy, changing the Primary Server tab address to the new SEC instance. The Default policy is applied to all boxes.

Under the new SEC instance in Update Manager, we added the new source location (pointing to new SEC).

The endpoints still are pointing to the old SEC instance. Their details show they are 'Awaiting policy transfer' under the 'Updating policy' field.

David
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 3 years ago in reply to David Lewis1

Hello David,

not sure what you see. The screenshot is from the new SEC? Did you configure the CID on the new server, i.e. added mrinit.conf pointing to the new SEC to the \savxp\rms\ subdirectory?

Christian
Cancel
Vote Up 0 Vote Down

Cancel
0 David Lewis1 over 3 years ago in reply to QC

Hi Christian,

We have not performed that. Could you point me to the right documentation to attempt this?

David
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 3 years ago in reply to David Lewis1

Hello David,

just changing the update location normally does not suffice. RMS is independent of the update location.
I assume you have re-used the old certificates. You can then follow section B in this article. See this article for other ways to redirect the endpoints.

Christian
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 QC over 3 years ago in reply to David Lewis1

Hello David,

just changing the update location normally does not suffice. RMS is independent of the update location.
I assume you have re-used the old certificates. You can then follow section B in this article. See this article for other ways to redirect the endpoints.

Christian
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data