If the password is greater than 8 characters, this can cause a problem in DOS.  You either need to change the password to less than 8 characters or switch to Linux or WinPE.

Thanks bhawver, i did a test, i create a new account (test), and i give a new pass (123456), i rebuild the bootwork DOS and type the date of the new account and new pass, i give permission in the folder deployment server of my RDP for the new account (full control), and i send again the job, but send the same message.

Any idea about that ??

Thanks

Teryus

 bhawver mentioned the most common reason for DOS failure -the password length.  Another aspect though is your server's local security policies. Sometimes, if you are part of a domain you might find that your domain administrator has set some stringent policies.

In particular check,

Network security: LAN Manager authentication level -should be "send LM and NTLM responses"

Hi,

Is your Deployment Server running on a Domain Controller or just using a policy that disalloves SMB signing? In this case you could try the following:

1. Start the Registry Editor (Regedit.exe)
2. Move to HKLM\System\CurrentControlSet\Services\lanmanserver\parameters
3. From the Edit menu select New - DWORD value
4. Add the following two values EnableSecuritySignature and RequireSecuritySignature if they do not exist.
5. Set the value of both the EnableSecuritySignature and RequireSecuritySignature DWORD to 0.
6. Close the registry editor
7. Restart the server

Please note: With SMB Signing disabled, it can open up "man-in-the-middle" attacks that could allow an attacker to disrupt a facility by which security settings are applied to Windows-based computers in a corporate network. This could allow the attacker to loosen settings on his or her own computer or impose tighter settings on another computer. Microsoft does not recommend disabling this setting.

I remember something.

In the paste, we have a RDP 3.5,  i dont install that RDP (3.5), but i install the new version 6.9

In the RDP 3.5 we have job DOS, but, when i send that job, i have to push F2 in the screen, that option send me to Bootworks, i push exit, and the job send me to a drive atach (F:)
In that drive, i type RDEPLOY and AMOUSE, after that i can create my image.

Well, we have do the same thing in the new rdp(6.9)

I check and i try everything you say me, but dont work,  but i remember in the old version DOS job its work.

Please, any idea about that

PD: Sorry for my english, its to bad, really to bad

How meny partitions do you have on your server BL40p? In case you have 4 or more partitions that could also cause some problems. C, D, E, F drives on the BL40p and it doesn't matter what you leter you have given them in the OS. Because you are then trying to map a drive using the same letter as you allready have.

Can you run the DOS boot on other servers without problems?

Hi, mlogan

I have a RAID 5, with 3 Disks of 36 GB each one, and not, the DOS bootwork dont work in other servers (I have BL20P and BL40P servers).

The option F2 to enter to bootworks, why the job don show me ??

Hi mlogan,

Yes, i have a C drive in my server
But, how can enable the option F2 to connect to F drive ???
In the old RDP we can do that, in this version 6.9 i dont have that option in screen.

Now, how can i make image to backup to much fast ???, i use Winpe by default
Exist some kind to tuning to RDP ????

Exist a DOS version of Aclient ???, because i ignored, i that case, if i dont have that version of DOS, the bootwork never work ???
I have the version 6.9, by the same, i dont need boot for DOS ???

I have the same problem, however, reinstalling bootworks a second time always clears the password problem.  Still makes it impossible to do any remote imaging as I have to be in the same room to reboot the computer so it will do the second install.

Bryan

We are having the same issue and it seems to have progressively gotten worse.  We used to do the same as Bryan, where we would just turn it off and it would work the second time.  Now, after the first time, when we turn it off and back on we get the message "Error: Unable to load boot loader."  We then need to flash it with the factory image via USB and then repeat the process.

Also, after they are up and running, any time you restart the unit it give the same "Access is Denied" message and asks for the password.  When this happens, the user needs to turn the unit off and back on for it to boot to production.

This all started happening after we upgraded from 6.8 to 6.9.  Wee needed to do so because our new CE boxes are CE 6.0 (old ones were 5.0) and 6.8 doesn't work with CE 6.0.

Still trying to figure this one out if anyone has any suggestions or solutions!

Tony

We are having this problem also. It started after upgrading from 6.8-6.9
It is an intermittent issue and get it about 10% of the time, but we do everything remotely, so this causes a huge problem for us.

We have a job to install bootworks using an install package, then a script to reimage the PC from a local NAS deice using rdeployt, then another script to uninstall bootworks.
All this worked perfectly untill version 6.9, and now 1 in 10 PC's will install bootworks and then stop at the connecting to the express share and ask for a password to \\SERVERSHARE\EXPRESS

If we manually reboot and run this job again 95% of the time it will work fine.

We are not sure what is causing this. we have tried recreating the bootworks packege to use the latest 6.9 files/components. We have checked permissions on the EXPRESS share, but they are wide open. We were thinking it is something on our network getting in the way f this prosess, but it looks like others are having this issue.

Look forward to hearing from anyone with some suggestions.

APN