dominicbastone Posted February 9, 2015 Posted February 9, 2015 Hi All, We have got rm cc4 have recently core upgrading one of our laptops and it has come up with Update Failed and it does not allow anyone to login anymore it does not have the login options. IN RMMC you can see the update has got so far and just stopped and does not seem to be going any further. Does anyone know of a way that we can get this laptop to either carry on the update or get us to the login screen?
Dkeen94 Posted February 9, 2015 Posted February 9, 2015 Have you tried pushing the update out again by finding the laptop > Right Click > Update system packages? If this doesnt work, rebuild.
foofighterjim Posted February 9, 2015 Posted February 9, 2015 When this happens and it specifies update failed with no logon options I have always rebuilt. I know in certain scenarios you can copy the core update to the workstation and run it manually but obviously you need to be able to login to do that.
rad Posted February 9, 2015 Posted February 9, 2015 I had to rebuild 17 the other day in one room, they all failed.
Edu-IT Posted February 9, 2015 Posted February 9, 2015 When this happens and it specifies update failed with no logon options I have always rebuilt. I know in certain scenarios you can copy the core update to the workstation and run it manually but obviously you need to be able to login to do that. If you disable one of the services, LogonUI I think it is, you can then reveal the login screen again and then log in to try a manual upgrade / fix on whatever is broken.
Chris_ Posted February 9, 2015 Posted February 9, 2015 The normal Windows 7 login screen is there, just you can't see it. The cursor should be focused on the username field so you can enter that, tab to the password field, press enter and wait, should log you in, you can then manually run the RM Core Upgrade, alternatively just rebuild!
bodminman Posted February 10, 2015 Posted February 10, 2015 We had an issue the other week with core updates and I ended up having to rebuild a load of PCs.
foofighterjim Posted February 10, 2015 Posted February 10, 2015 Always worth just doing a handful of workstations at a time, when core updating I never do more than 15 in one go.
HTCPCP Posted February 13, 2015 Posted February 13, 2015 We had that recently with a couple of machines in the latest batch of updates, and a rebuild kicked it through and installed the updates. I tend to do the updates in rooms/trolleys, so a maximum of 31 if we do an IT suite, or 16 if we do a trolley. It seems that machines where you haven't updated for a long time are more likely to fall over when doing it (so the machines are the ones that we didn't get around to rebuilding last summer, so haven't been rebuilt since they were originally built probably around 3 years ago unless they have failed for what ever reason.
Duranis Posted May 16, 2016 Posted May 16, 2016 Sorry to necro post but having the same issue. Out of 8 systems I have updated so far 6 of them have failed like this. Can get logged into them but cannot see where the core update is located on the server to try and manually copy it over and install it. RMMC is also pretty useless as it is showing that they are still in progress despite them having been sat with the update failed message on screen all day.
Kenny_G Posted May 16, 2016 Posted May 16, 2016 We had the same issue, after disabling the LogonUI services we then followed tech article TEC4523113 and this worked for us.
Duranis Posted May 16, 2016 Posted May 16, 2016 We had the same issue, after disabling the LogonUI services we then followed tech article TEC4523113 and this worked for us. Brill' thanks. Will take a look at that tomorrow. I really don't wont to have to rebuild all these machines.
AXE Posted May 17, 2016 Posted May 17, 2016 Had pretty much a 100% failure rate. I've found that there are a lot of things that cause core updates to fail. #1: If you've ever used a tool to clean user profiles off a PC, it's pretty much guaranteed to fail. #2: If you've ever installed\reinstalled Internet Explorer or Java, it's pretty much guaranteed to fail. It's left me only with the option of doing full rebuilds now every time there is even a minor issue. It also doesn't help much when every ticket I open with RM support ends up with the suggestion to either 'Core Upgrade ALL of your PCs' or simply 'Rebuild ALL of your PCs'.
jonspurs Posted May 27, 2016 Posted May 27, 2016 Had some failing - due to "RM Add Local User Group". This meant we had to manually assign that package prior to core upgrading. It'd show red exclamation marks, but you 'clear status' in the assignment overview and allocate again. Either this or rebuilding.
Poults Posted June 9, 2016 Posted June 9, 2016 The normal Windows 7 login screen is there, just you can't see it. The cursor should be focused on the username field so you can enter that, tab to the password field, press enter and wait, should log you in, you can then manually run the RM Core Upgrade, alternatively just rebuild! I found manaully copying the core upgrade to the station and then running an rdp to it let me login and manage to run the update on the majoirty of the stations i tried it on.
IT_Man_Dan Posted May 8, 2019 Posted May 8, 2019 Sorry to resurrect an old thread but can someone point me to the location of the core updates for the workstations? I've got a couple of rubbish "Failed Update" screens. Can rdp on and want to try and manually rerun the update to see if it fixes it. Thanks Dan
BOOT Posted May 8, 2019 Posted May 8, 2019 This is what I use to clear a failed core upgrade... REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Core Logoff" /f REG DELETE "HKLM\SOFTWARE\Wow6432Node\RM\PackageInitialisation" /v "Core Logoff" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "BlockLogon" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Package Title" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Package Status" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "CmdExecPause" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "RollBackIA" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Bootstrapper Description" /f REG ADD "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Bootstrapper Heartbeat" /t "REG_DWORD" /d 0 /f REG ADD "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Bootstrapper Status" /t "REG_DWORD" /d 3 /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "BlockLogon" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Package Title" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Package Status" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "CmdExecPause" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "RollBackIA" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Bootstrapper Description" /f REG ADD "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Bootstrapper Heartbeat" /t "REG_DWORD" /d 0 /f REG ADD "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Bootstrapper Status" /t "REG_DWORD" /d 3 /f 1
IT_Man_Dan Posted May 8, 2019 Posted May 8, 2019 This is what I use to clear a failed core upgrade... REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Core Logoff" /f REG DELETE "HKLM\SOFTWARE\Wow6432Node\RM\PackageInitialisation" /v "Core Logoff" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "BlockLogon" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Package Title" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Package Status" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "CmdExecPause" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "RollBackIA" /f REG DELETE "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Bootstrapper Description" /f REG ADD "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Bootstrapper Heartbeat" /t "REG_DWORD" /d 0 /f REG ADD "HKLM\SOFTWARE\RM\PackageInitialisation" /v "Bootstrapper Status" /t "REG_DWORD" /d 3 /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "BlockLogon" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Package Title" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Package Status" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "CmdExecPause" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "RollBackIA" /f REG DELETE "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Bootstrapper Description" /f REG ADD "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Bootstrapper Heartbeat" /t "REG_DWORD" /d 0 /f REG ADD "HKLM\SOFTWARE\WOW6432Node\RM\PackageInitialisation" /v "Bootstrapper Status" /t "REG_DWORD" /d 3 /f Thanks that got me in but I still am unable to push out the update or restart the pc from the console. Any ideas? Thanks
BOOT Posted May 8, 2019 Posted May 8, 2019 You could try reinstalling the RM Serialization Helper.msi in: C:\ProgramData\RM\Connect\RMCoreUpgrade\CC4 Components\RM Serialization Helper
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now