Ghost & Server 2003

Hello, does anyone know if it is possible to have a ghost directory on a
Windows 2003 server that is accessable from a DOS boot disk? If so, how??

Thanks!

Yes. But you need a DOS bootdisk with the right network drivers. I've used
http://www.netbootdisk.com/ with success.

Or you can use BartPE to burn a bootable CD with even more options:
http://www.nu2.nu/pebuilder/.

"Eric Fehlhaber" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello, does anyone know if it is possible to have a ghost directory on a
> Windows 2003 server that is accessable from a DOS boot disk? If so, how??
>
> Thanks!
>

Thanks Mike, I actually already use netbootdisk. (I have been for some time
now actually!) It works great with Windows 2000 servers. I am easily able
to map to a shared directory, run the ghost.exe, and ghost PCs. I am unable
to do this if the shared directory is on a Windows 2003 server. My guess is
that it is some kind of a security feature or something that I need to learn
how to turn off...

I also use Bart's in some instances, but for ghosting it takes too long to
boot to use.



"Mike Lowery" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Yes. But you need a DOS bootdisk with the right network drivers. I've
> used http://www.netbootdisk.com/ with success.
>
> Or you can use BartPE to burn a bootable CD with even more options:
> http://www.nu2.nu/pebuilder/.
>
> "Eric Fehlhaber" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hello, does anyone know if it is possible to have a ghost directory on a
>> Windows 2003 server that is accessable from a DOS boot disk? If so,
>> how??
>>
>> Thanks!
>>
>
>

"Eric Fehlhaber" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks Mike, I actually already use netbootdisk. (I have been for some
time
> now actually!) It works great with Windows 2000 servers. I am easily
able
> to map to a shared directory, run the ghost.exe, and ghost PCs. I am
unable
> to do this if the shared directory is on a Windows 2003 server. My guess
is
> that it is some kind of a security feature or something that I need to
learn
> how to turn off...

No. It is because DOS cannot read and NTFS partion,...it can only read FAT16
(up to DOS6.22). If the DOS boot disk is made from one of the Win98
variations (which is newer than DOS6.22) then it can read FAT16 & FAT32.

You Server would have to have a FAT partion for this purpose. But I never
do that,...there is most certainly a better approach than what you are
attempting.
One of my big rules is, "If it is very hard to do, you are probably doing it
wrong" :-)

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

A good compliment cliché to your saying is simply, "there has GOT to be an
easier way!"

Anyway, do you have any suggestions? I am currently exploring the GhostCast
features of Ghost Solutions Suite 1.1. Has anyone set this up and
implemented it? Does it work better than the traditional ghosting method of
using a boot disk and recovering an image from a server?

Additionally, I did some checking and all our severs are setup with NTFS
file systems. Including the ones that I am able to currently connect to via
netbootdisk.

Any other suggestions??

Thanks!

Eric


"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...
> "Eric Fehlhaber" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Thanks Mike, I actually already use netbootdisk. (I have been for some
> time
>> now actually!) It works great with Windows 2000 servers. I am easily
> able
>> to map to a shared directory, run the ghost.exe, and ghost PCs. I am
> unable
>> to do this if the shared directory is on a Windows 2003 server. My guess
> is
>> that it is some kind of a security feature or something that I need to
> learn
>> how to turn off...
>
> No. It is because DOS cannot read and NTFS partion,...it can only read
> FAT16
> (up to DOS6.22). If the DOS boot disk is made from one of the Win98
> variations (which is newer than DOS6.22) then it can read FAT16 & FAT32.
>
> You Server would have to have a FAT partion for this purpose. But I never
> do that,...there is most certainly a better approach than what you are
> attempting.
> One of my big rules is, "If it is very hard to do, you are probably doing
> it
> wrong" :-)
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...

> No. It is because DOS cannot read and NTFS partion,...it can only read
> FAT16
> (up to DOS6.22). If the DOS boot disk is made from one of the Win98
> variations (which is newer than DOS6.22) then it can read FAT16 & FAT32.
>
> You Server would have to have a FAT partion for this purpose. But I never
> do that,...there is most certainly a better approach than what you are
> attempting.
> One of my big rules is, "If it is very hard to do, you are probably doing
> it
> wrong" :-)
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

I'm not sure how to help the OP, but I don't think his problem has anything
to do with the filesystem on the server as it sounds like he's accessing it
via a network share. As an example, a Win 95 client can access a shared
that has it's data on an NTFS partition just fine even though Win95 can't
read NTFS. The network client and server services take care of that for
you.

Gotta be a different problem.

My guess is that it caused by the increased security in W2k3. By default
it requires mschapv2, I think. So DOS is a non starter.

I always use a win2k3 server as fileserver for my images. I use bart's
bootdisk. First I couldn't access the share neither, till I made a non-domain
user on the server and gave it access to the share. Without logging in on the
domain I could access the share from dos.

Later on I successfully logged in onto the domain, and could access other
shares too.

Btw, make very sure you have the best drivers you can get for your nic, I
had loads of weird problems using a slightly wrong driver....

"Bill Grant" wrote:

> My guess is that it caused by the increased security in W2k3. By default
> it requires mschapv2, I think. So DOS is a non starter.
>
>
>

It's definitely not a problem with using NTFS.

I've had problems getting the bootdisk to connect to shares on Win2003 myself
and eventually had to do what Nico said: Create a local account with a simple
password. I may have made some group policy changes too. It was very confusing
but I eventually got it working.

"Nico" <(E-Mail Removed)> wrote in message
news:145AE368-9EE9-4A60-953A-(E-Mail Removed)...
>I always use a win2k3 server as fileserver for my images. I use bart's
> bootdisk. First I couldn't access the share neither, till I made a non-domain
> user on the server and gave it access to the share. Without logging in on the
> domain I could access the share from dos.
>
> Later on I successfully logged in onto the domain, and could access other
> shares too.
>
> Btw, make very sure you have the best drivers you can get for your nic, I
> had loads of weird problems using a slightly wrong driver....
>
> "Bill Grant" wrote:
>
>> My guess is that it caused by the increased security in W2k3. By default
>> it requires mschapv2, I think. So DOS is a non starter.
>>
>>
>>

"Phil McNeill" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm not sure how to help the OP, but I don't think his problem has
anything
> to do with the filesystem on the server as it sounds like he's accessing
it
> via a network share.

Can't. DOS won't access shares on a Server2003 box without disabling some
of the feature that were added to 2003.

This article doesn't mention DOS, but it is the same thing.

811497 - Error Message When Windows 95 or Windows NT 4.0 Client
Logs On to Windows Server 2003 Domain
http://support.microsoft.com/default...b;en-us;811497


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------