I'd like to know why sometimes when I boot up my machine does it take some time for it to become responsive, i.e., numlock and capslock keys are disabled and the only way out is to press CTRL + ALT + DEL.

That has nothing to do with powershell, now does it? Misleading topics are not ok and if you do it again your posts will be deleted. And as far as the question goes we'll need some more information: Hardware Operating system (ie which version of Windows Server 2008 are you running) Is it before it comes to windows bootsequence or during it?

In regard to my question about the Windows Server, as posted in the windows.server newsgroup (NNTP) the OS loads up however the only interaction possible is to press CTRL + ALT + DEL and then press cancel. Do you know why this behaviour exists?

The CTRL+Alt+Delete keystroke is "by design" but if it's a single user system you could always make the server login automatically. If I understand your problem correctly you can press Ctrl+Alt+Delete, but then do nothing but press cancel which leaves you at the logon screen, correct?

Hi Joachim, The server does log in automatically which I found to be very convenient and different from anything else I've tried, however then it started becoming unresponsive and I had no idea why so I re-installed it under safe mode and the same thing happened on next reboot until I worked out that using SAS I could get back to the main login screen and then work from there but I think more work needs to be done on that aspect of the OS because merely having to hit Cancel seems to be a poor workaround to me. Thank you

It will only login automatically until you've completed the initial configuration screen. What features/roles have you added?

The only feature I have active is the Desktop Experience because I'm using it as a workstation similar to Windows Server 2003 before it became XP and I appreciate it very much that now many of the services which once were enabled by default are instead disabled and as such the firewall, which I find to be a most useful feature of Windows is now enabled by default, as I believe it should have been always from the start and no roles defined until I am ready to test them. The only thing I don't like is the MMC appers not to uniform throughout the entire management flow.

What makes it go slower over time could be your profile growing then, like a lot of documents / data on the desktop for instance. I agree that a lot of things are changed to the better regarding services being enabled or disabled by default. The MMC's will probably be uniform by release (we hope )

That would be excellent if the MMC's were all uniform I agree and I really hope by release time they are because carrying over legacies such as that only makes it more difficult for them to be changed in the future and I hope you agree with me on this and will put forward a strong case for change on behalf of future users of Windows OS. Another legacy I don't enjoy without having to start a new thread would be that I can't type in for example services at the run command and have the appropriate Microsoft Management Console appear, however for some reason I can for the eventvwr MMC. Can someone please explain this inconsistency and address it in due course, as well as .cpl files being executed in the same way? Thank you

That's interesting because when you are in the Task Manager you can't go directly to the service it is attached to (of course if there is one attached) and it would be yet another nice thing for windows to have.