We recently decided to upgrade from 9.2.5 to 9.2.6 and install it on the D-drive instead of the C-drive (our D-drive is easier expendable).
One thing that isn’t migrated is the UMS. We tried to do that with the fixlets, but without success. When we run the Uninstall or the Upgrade (doesn’t matter), the status of the action is completed but if we check “Show Action Info”, it says failed next to the first line.
That fixlet is referencing a registry key value which is used as a parameter for location.
parameter "MFS_FOLDER"="{ value "EnterpriseServerFolder" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server" of registry as string & "Applications" }"
I would investigate why that Registry Value has not changed…
If you want to do be wild, then you could try uninstalling UMS, Changing the Value in the registry, then installing the UMS again.
-jgo
Thanks for your answer. I did your relevance in the QnA:
Q: value "EnterpriseServerFolder" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server" of registry as string & "Applications"
A: D:\Program Files (x86)\BigFix Enterprise\BES Server\Applications
T: 0.159 ms
so it does refer to the D:.. As it should be. So any other idea?
Some more info that can help you out:
This is what we get when we upload it:
The files are in the uploads:
[Wed Feb 3 15:34:13 2016] SWD Download Plugin v1.3.1
[Wed Feb 3 15:34:13 2016] Please make sure you have the latest version of this utility.
[Wed Feb 3 15:34:13 2016] ERROR: Download for SWDProtocol://127.0.0.1:52311/Uploads/DE1AA77DD1BD8DF6DC293E5332CAEC92D27C2371/file failed: Setup failed: SHA1 directory does not exist: 'C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\\Uploads/DE1AA77DD1BD8DF6DC293E5332CAEC92D27C2371'
I checked the Uploads on the C:, but it’s not there (because it’s on D: as mentioned in previous screenshots…)
So I do find it strang that this still refers to the C:.. and not the D:.. although it uploads to D:…
Same issue here. After running the plugin exe the log file was created. Somehow this utility is not the latest? Have you found the issue?
I’m encountering it with the deployment for a task…
Yes, my issue was that we reinstalled our environment from C:\ to D:\ so we came accross a couple of problems.
Some processes where started on the C: but should be started on the D: etc. So if that’s your issue, check all your processes and services and make sure the correct one is running.
That solved it for me… But i’m guessing you have another issue with it?
Thank you. The issue on my side is probably different since the last action within the environment was an update for IBM BigFix. Will check as this seems to impact some deployments.
Finally the answer for my issue was that all BES Services must use an account with high level access - I used the administrator BUT if this is encountered within a production environment then the best thing to do is the use of a service account created only for BigFix purposes.
Good luck!
