{"id":416,"date":"2010-01-19T13:20:20","date_gmt":"2010-01-19T13:20:20","guid":{"rendered":"http:\/\/salientsoft.co.uk\/?p=416"},"modified":"2010-01-23T11:23:52","modified_gmt":"2010-01-23T11:23:52","slug":"windows-xp-home-workgroup-remote-administrationshutdown","status":"publish","type":"post","link":"https:\/\/salientsoft.co.uk\/?p=416","title":{"rendered":"Windows XP Home Workgroup Remote Administration\/Shutdown"},"content":{"rendered":"

Unfortunately XP home does not have a remote registry service, so remote admin is limited.
\nYou cannot remotely view the event log for example. You can however remotely shut down an XP home computer.<\/p>\n

XP home remote admin is governed by the ForceGuest registry setting, whereby remote connections are forced to be guest access even if the connection is with other credentials such as an administrator. for XP pro this is on by default, but for XP home it cannot<\/strong> be turned off – it appears to be a side effect of xp home simple file sharing<\/strong>, which also cannot be turned off. You can however get around this for remote shutdown, but only by making the Guest account an administrator, which carries significant\u00a0risk (it will allow any PC on the workgroup to shutdown the target pc) but within a small family\u00a0home workgroup may be deemed acceptable. Do this as follows :-<\/p>\n

    \n
  1. To make Guest an administrator, enter Start\/Run\/Control userpasswords2<\/strong>. This opens the advanced user management control panel applet, from which you can open the properties for Guest<\/strong> and add it to the administrators group (you must also enable the account – it is disabled by default).<\/li>\n
  2. Unfortunately, a side effect of this is that Guest<\/strong> then appears on the login screen, which in this case we definitely do not want. You can remove Guest from the login screen by\u00a0adding the following registry\u00a0value\u00a0as a DWord<\/strong> with\u00a0a value of\u00a00 (zero)<\/strong>\u00a0:-
    \nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\WindowsNT\\CurrentVersion\\Winlogon\\SpecialAccounts\\UserList\\Guest
    \n<\/strong>Note that this<\/strong><\/a>\u00a0<\/strong>forum post describes the process.<\/li>\n
  3. Having performed these steps, you can then use the shutdown<\/strong> command from another machine in the workgroup. Shutdown \/i<\/strong>\u00a0 from a command prompt will open gui mode which is more friendly, but this does not appear to allow the force (\/f) option which forces application shutdown if apps are running. The following example will perform an immediate forced shutdown of the pc named TargetPC<\/strong> with a reason of “planned hardware maintenance” :-
    \nshutdown \/s \/f \/m <\/strong>    \\\\TargetPC<\/a><\/strong> \/t 0 \/d p:1:1<\/strong><\/li>\n
  4. You can add the command to a batch file, but do not<\/strong> do as I did and name the file shutdown.bat<\/strong>, otherwise it will recursively call itself rather than perform the shutdown command!<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    Unfortunately XP home does not have a remote registry service, so remote admin is limited. You cannot remotely view the event log for example. You can however remotely shut down an XP home computer. XP home remote admin is governed by the ForceGuest registry setting, whereby remote connections are forced to be guest access even […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[41],"tags":[16],"_links":{"self":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/416"}],"collection":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=416"}],"version-history":[{"count":5,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/416\/revisions"}],"predecessor-version":[{"id":435,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/416\/revisions\/435"}],"wp:attachment":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=416"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=416"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}