@Quazz said in Deployement failed on smaller drive (message "Target partition size smaller"):

I’ve made it a habit to just start over every time.

We also find the same thing and create new every time.
FWIW: We use MDT to build the reference image, that way we have a consistent way to “start over every time”.

@Tom-Elliott

Thanks alot for pointing out on the nic cannot get an ip. we have did some digging on fog wiki and found out it is network switch issue.

Thanks alot again.

So I was able to do a “Full disk Repair” and then use command line to shut down the system which seemed to fix the error I was having and am now doing a successful capture! Thank You!

@mtanigawa lol, what would you suggest to make it infiltrate better? I can change the article if you can come up with something better.

@george1421 I have removed the the global parameters and still exhibiting the same behavior. It is weird that this happened right after I made that change. I think something might have gotten corrupted, but I am not sure what to do at this point.

@SquidgyHobo RHEL 5.3 isn’t supported by FOG.

RHEL 5.3 also it went EOL from Redhat Jan 2011. I would not even use that in my environment since it is susceptible to a handful of nasty and well publicized vulnerabilities.

RHEL / Centos 6.5+ and 7.x are currently supported, as well as the Debian variants.

I downloaded the package again and the installation worked.

I don’t know what happened but its now working.

HenryI did an experiment, a simple multicast send and receive on a private network contains only the Access Point and one station. The results are:

With the station sends and the Access Point receives multicast data using 224.0.0.1, the rate is over 20 Mbit/sec. With the Access Point sends and the station receives multicast data using 224.0.0.1, the rate is over very slow even less than 2 Mbit/sec.
I have no clue!!

@george1421

Awesome! It works!

Thanks a lot.

I’ll have a look at dmidecode when things settle down a little thanks.

@Tom-Elliott
@george1421 after updating to the latest version the deployments to the NCR still fail. I am able to image PCs and laptops so I will just use a different solution for the NCRs and leave it at that. Thanks everyone for all of your help and assistance!

Thanks,

Anthony

You can also turn off DHCP config generation by setting bldhcp to 0 in .fogsettings

@Wayne-Workman said in After install FOG my user account's (fog) password seems not to work anymore:

@sdorion said in After install FOG my user account's (fog) password seems not to work anymore:

When I installed kubuntu I choose fog as username…

That was your first mistake. Do not create a user called fog, this is a reserved account.

The password for the fog account will be in storage management. Once in, I would advise you to make a different account called something else, and leave the fog account alone.

OK.
Thank you Wayne.

@Quazz said in Install script errors:

I’m wondering if Ubuntu updated Bash to be a bit different, hmmm.

They didn’t. The installer is tested on Ubuntu every day, you can see the test results here: http://perpetuum.io:20080/fog_distro_check/installer_dashboard.html

@Tom-Elliott we already had FOG_TASK_FORCE_REBOOT set but to no effect. I will try disabling it completely.
Btw. I cannot mark answers of others as correct…

@Tom-Elliott

Yes sir! Things are working well! I’ve multicasted several machines this afternoon without a hitch. Yay! Thanks!!

@Tom-Elliott
i’ts working with the fog server 1.4.4 SVN 6077.

Thanks a lot.

Can you unset the filter after “checking” the boxes to see if they’re all being checked accidentally?

@chief said in Windows 10 Enterprise Fog Client Install:

How do you install the Fog client so that on install it will boot, connect to AD etc?

Install it before going into audit mode.

When I was doing a lot of imaging, I didn’t sysprep. See this older post: https://forums.fogproject.org/topic/8906/to-sysprep-or-not-that-is-the-question

@Tom-Elliott

It was on Raid, so I changed to AHCI. No Joy, still get the same message.

Ok…well not sure why or how I had a couple of machines showing that same error…but I started rebuilding a different machine from the OS up and it captured with no problems. Thanks for your help.