Installed a new OSD server,
It’s always failing a Update Driver Manifests on Bare Metal Servers:
Failed continue if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 >= 1518182235014}
When I look in the manifestimport.log file on the server, it shows this error.
Can somebody help me with this?
It’s the only server that’s unable to sync all others have no issue’s with this.
Good job obscuring the screenshot, but I think we might need to see the filename (not server name). Is it an image file, a PE WIM, or one of the binding grid files? Does the referenced file actually exist on your BES server?
I had a similar issue a while back when I once had a driver bound to Windows XP, and later removed all bindings for XP. The OSD Dashboard Variables would not delete the prior value and bare metal server sync was trying to download a binding grid that no longer existed.
Hi Jason, thanks for your reply.
It’s a BFOSD file: .com:52311/Uploads/d2cfb08af6441fa4389114208e6b407543f6d9da/D2CFB08AF6441FA4389114208E6B407543F6D9DApkg.BFOSD/D2CFB08AF6441FA4389114208E6B407543F6D9DA|3613604|D918DEF305079CD2ABCAA6D9CD45DB841C86032CD192C5E1C0C109941BA9829C/D2CFB08AF6441FA4389114208E6B407543F6D9DApkg.BFOSD
When I look onto the main server, I see that file in the uploads folder: D:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\Uploads\d2cfb08af6441fa4389114208e6b407543f6d9da\D2CFB08AF6441FA4389114208E6B407543F6D9DApkg.BFOSD
The relay is set to get it’s source files from the main server. What I don’t get is why other OS deployment servers are able to get that file?
I think you’ll need to open a PMR and collect some traces to troubleshoot this one.
