Server 2012 R2 - the request to add or remove features failed
-
I am having a frustrating time adding Remote Access role to my 2012 R2 domain controller (HyperV VM)...
It keeps failing with THE REQUEST TO ADD REMOVE FEATURES FAILED
I've tried repairing my component store with no luck...it keeps telling me the server requires a restart.
Could this have ANYTHING to do with the host machine needing a reboot? That is one thing I've not tired yet.
-
How are you restarting the server? That message you are seeing means you have not restarted, or restarted properly. Are you logged into that server that you are working on or are you on another system working with Server Manager?
-
@Bill-Kindle said:
How are you restarting the server? That message you are seeing means you have not restarted, or restarted properly. Are you logged into that server that you are working on or are you on another system working with Server Manager?
I've restarted the Server (VM) at the console on the host several times. It keeps coming back with it needs a reboot.
-
@garak0410 said:
@Bill-Kindle said:
How are you restarting the server? That message you are seeing means you have not restarted, or restarted properly. Are you logged into that server that you are working on or are you on another system working with Server Manager?
I've restarted the Server (VM) at the console on the host several times. It keeps coming back with it needs a reboot.
Don't restart that way.
Open up a powershell prompt and type this in:
restart-computer
and press enter.
-
@Bill-Kindle said:
@garak0410 said:
@Bill-Kindle said:
How are you restarting the server? That message you are seeing means you have not restarted, or restarted properly. Are you logged into that server that you are working on or are you on another system working with Server Manager?
I've restarted the Server (VM) at the console on the host several times. It keeps coming back with it needs a reboot.
Don't restart that way.
Open up a powershell prompt and type this in:
restart-computer
and press enter.
Trying now...
-
@garak0410 Run that cmdlet only on the VM, not the host machine or you will reboot the entire hyper-visor.
-
@Bill-Kindle said:
@garak0410 Run that cmdlet only on the VM, not the host machine or you will reboot the entire hyper-visor.
For sure...
-
Same problem...says the server needs to reboot.
This is very odd since this is a very new VM with nothing really changed on it...
-
@garak0410 said:
Same problem...says the server needs to reboot.
This is very odd since this is a very new VM with nothing really changed on it...
Are you 100% positive you are on the correct VM and not accidentally working on a different VM from this VM's server manager?
-
@Bill-Kindle said:
@garak0410 said:
Same problem...says the server needs to reboot.
This is very odd since this is a very new VM with nothing really changed on it...
Are you 100% positive you are on the correct VM and not accidentally working on a different VM from this VM's server manager?
Yes sir...I've done this both through remote desktop and on the console for this server on the host...same darn error each time I try to add REMOTE ACCESS role...
-
-
@alexntg said:
Looking at this now...I do have this key and there is a file located at the directory that it lists as PendingFileRename called 9a072afe.BUD...deleting the key and rebooting.
-
@garak0410 said:
@alexntg said:
Looking at this now...I do have this key and there is a file located at the directory that it lists as PendingFileRename called 9a072afe.BUD...deleting the key and rebooting.
Deleted key...rebooted...retried the feature install...same problem...checked to see if PendingFileRename came back and it didn't.
-
I hate to say it.. but if time is an issue, and there is nothing else on this server (which it sounds like since you can reboot it 20 times a day) why not just build another VM and scrap this one? If you want to save it for later and try to trouble shoot it when you have nothing better to do.. Ok do that.
-
@Dashrender said:
I hate to say it.. but if time is an issue, and there is nothing else on this server (which it sounds like since you can reboot it 20 times a day) why not just build another VM and scrap this one? If you want to save it for later and try to trouble shoot it when you have nothing better to do.. Ok do that.
Whew...would hate to have to do this...it is already sharing duties with the soon to be demoted old domain controller...I can't imagine what would cause this problem since I keep this machine very clean.
-
@garak0410 said:
@Dashrender said:
I hate to say it.. but if time is an issue, and there is nothing else on this server (which it sounds like since you can reboot it 20 times a day) why not just build another VM and scrap this one? If you want to save it for later and try to trouble shoot it when you have nothing better to do.. Ok do that.
Whew...would hate to have to do this...it is already sharing duties with the soon to be demoted old domain controller...I can't imagine what would cause this problem since I keep this machine very clean.
The upside is that you can have effectively unlimited domain controllers all "sharing duties." Adding another one isn't a problem.
