Re: Scheduling Tasks in Windows XP Professional with a no password acc
- From: "Doug Knox MS-MVP" <dknox@xxxxxxxx>
- Date: Tue, 27 Jun 2006 11:27:53 -0400
Instead of using the mapped drive letter, use the UNC format. This will allow the task to work whether the account is logged on, or not.
\\<machinename>\<sharename>\<path>
Alternatively, you can set Group Policies to allow blank passwords, but this creates a security hole, as even remote Desktop would work for an account with no password, as long as they know your username. It also creates other vulnerabilities.
Click Start, Run and enter GPEDIT.MSC Go to Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options. In the right pane locate Accounts: Limit local account use of blank passwords to console logon only. Double click this item and set it to Disabled.
--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
"DBost" <darin.bost@xxxxxxxxxxxxx(donotspam)> wrote in message news:18DB43FE-2818-4583-9A83-0310A22FDFCA@xxxxxxxxxxxxxxxx
Recently I received a new PC with Windows XP Professional to replace an.
existing leased PC with Windows 2000. This PC runs a scheduled task once per
day to activate a batch file to copy data over from another network PC.
The user account for operations does not require a password. As far as I
can tell, Windows XP requires a password to schedule a task (null for
password does not work). So, to get around this little Windows issue, I
created a new administrative account w/ pw and under the user account, I
scheduled the task with "Run as" the administrative account. The scheduled
task worked, calling the batch file. However, the batch file did not
complete (probably because the batch file has a mapped drive - mapped
identically for both accounts, but when not logged onto the admin account the
drive is disconnected).
So, if I am logged onto the admin account the batch file runs correctly. If
I am logged onto the user account the batch file will not complete. I would
prefer to only have one account - the user account with no password.
Does anyone see a way around either the scheduling issue or the mapped drive
issue? Thanks in advance.
--
D
- Prev by Date: Re: some advise
- Next by Date: Re: Can't open word file
- Previous by thread: Reading Index.dat
- Next by thread: Re: Scheduling Tasks in Windows XP Professional with a no password acc
- Index(es):
Relevant Pages
|
Loading
