Ghost Solution Suite

So I have a pxe boot into WinPE (windows 10) I have my ghostcast setup to allow the session.

Once my 20th machine connects to the ghostcast session, the next machine I launch will connect to the pxe and the get to the command prompt screen it connects to DHCP but will get hung up on the command prompt screen when it is trying to connect to the M share it will hang here for a while till it times out. 

so it gets hung up here

When it works right it should look like this

Anyone know what causes this limitation of 20 to only connect?

Michael,

There is not a 20 machine limitation in regards to ghostcast.

It looks to me like your dhcp server is running out of I.P.'s to hand out to clients, please check the server availability and verify.

It's not that because I have DHCP set to over 200 and I have only 21 machines I am testing this with. 

After further inspection I was able to get more of the command prompt before the pc turns off here the screen shot

So if it does not get an Ip it would not go to the Authenticating network connection. It would be stuck on looking for an Ip address

So what I see from this screen shot is that for some reason when the server hits 20 connections it won't let any more machines authenticate. Is there some setting or file somewhere that has a 20 limit I been looking through everything can't find it.

I used to boot from the flash drive and do this before we set up a pxe server with winpe and was able to do more than 20 so something doesn't add up.

Using Ghost soultion Suite 3.1 maintenance patched 5 on Windows 10 if that helps anything.

Like I said there is no limitation hard coded in Ghost or Ghost cast with this value. It looks to be like this machine never grabs a true i.p. from the dhcp.

Is this machine a different model?

Newer Machine?

If you don't boot one of the others and make the machine that is failing apart of the "20" will it work properly? If you boot the machine by itself without the other 20 will it work properly?

Duplicate post sorry

They are all the same laptop Model and if I do that one in the first 20 it will work then another random one won't connect and by itself it will connect fine.

It has an Ip I see the DHCP server showing the mac address for the machine with ip.

Like I was saying something is blocking the authentication.

I found this article

https://support.symantec.com/en_US/article.TECH26539.html

But it's not helpful because if this was not set up correctly it would not work on any machine. 

Michael,

I am glad it is not an issue specific to that machine.

Do me a favor and check your dhcp server to see the number of available leases. You said it has 200 in it's range but something is going on there. The way a pxe boot works is...

1. Contact dhcp server for i.p. address

2. authenticate against network share and map express share to M:\

3. Start Ghost and the start imaging.

If you machine is getting a 169 address then it is not being assigned a valid i.p. address from your dhcp server when you have 20 other machines booting.

As mentioned before pxe has no hard cap on the number of machines.

The thing is the part on the command part where it says "authenticating a network connection" will not come up if the machine has not gotten a valid ip it will keep trying to find one until it does.

I have multiple users, not just me, that have the same ghost setup on a different server at a different site that is telling me they get hung up on 20 as well. I tried 2 different dhcp servers programs so It has to be something else. 

Michael,

What Operating system do you have Ghost Solution Suite installed on.

Also,

Check the location in the below screenshot and make sure the user limit is set to unlimited. There may be a GPO limited sessions on your server...

Windows 10 Enterprise I was looking into something I think it could be related to Windows has a limit of 20devices can only connect to a share.

Is there some way to have the wim file have the Ghost64.exe local so that the laptops are not having to access a local share. Or is there a workaround for this?

https://social.technet.microsoft.com/Forums/en-US/c48275b9-c6b4-47ab-9f15-08f089342d4b/maximum-concurrent-connections-beyond-20?forum=WinPreview2014General

Michael,

Even if the ghost64.exe was local you would still be accessing the share to save images and the clients would still be opening a connection with the server. 

The only option I see if you wanted to do more machines at once would be to install Ghost Solution Suite on a server OS 2008 R2, 2012 R2. This would get rid of that connection issue you are having.