NEW Secondary Server Rebuild - Not Installing Apps During Task Sequence

[jhl_2012]

Hello,

Recently I had a Secondary site Server die. I deleted it out of SCCM, rebuilt it and recreated it back in to SCCM as a secondary site with the same name and IP Address.

Everything will work fine expect the installing apps step in the Task sequence for clients on this site.

I have rebuilt it several times to no avail.

Interestingly enough if I rebuild the server but using a name that hasn't been used before all apps deploy successfully during the task sequence.

So I have come to the conclusion that the original name is being held somewhere in the SCCM database even when the server has been deleted.

Can anybody recommend steps to rectify this so I can use the original name?

I am running 1902 Hotfix rollup.

Thanks

 

[Garth]

It will take several days for a computer to be removed from CM. Why reuse the server name in the first place?

 

[jhl_2012]

It will take several days for a computer to be removed from CM. Why reuse the server name in the first place?

The Secondary site server was only deleted as part of troubleshooting. We have a standard naming convention we need to adhere to thus wanting to keep the same name.

 

[Garth]

When you delete a computer in CM it isn't removed right away, it waiting until one of the maintenance task clean out old data, this take a few days, ~3 days.

 

[jhl_2012]

When you delete a computer in CM it isn't removed right away, it waiting until one of the maintenance task clean out old data, this take a few days, ~3 days.

I understand that, but I’m talking about a secondary site server not a client. I have removed it out of sites. Are you saying I need to wait a few days until I create it again as a secondary site server?