Posts made by KnightRaven

@lukebarone
Oh apparently its just a little further up the chain…
Using the same xml file you can customize both.
https://docs.microsoft.com/en-us/windows/configuration/configure-windows-10-taskbar

Jason

@lukebarone
I feel your pain. Win 10 just doesn’t play well with the old conventions of sysprepping it seems.
For the start menu, however, the closest I can see is to use a GPO and export the layout.
Try this site for details: Win 10 Customize and export Start layout
I’m not sure yet if there is a clean way to do the taskbar. We used a script that setup the links/pins for Win7. I havent tested yet if it work the same for 10.

just my $.02 worth. Hope it helps some.
Jason

Well, since you didn’t specify i’ll take a stab at the obvious first…
BIOS? Is it updated? Same across all PCs?
Have you tried moving slow PC to a known good network connection? Make sure cabling/switches etc aren’t the problem.

Have you tried rebooting when you notice it being slow?
I just had a Dell 780 not pickup DHCP at PXE Boot.
Had to remove power cable and clear the power(hit power button til nothing happened). After that it worked.
Maybe try clearing BIOS. Either through BIOS menu or using jumpers.

Are you sure you have exactly the same NICs? We have refurbs. While we haven’t had an issue with NICs it’s plausible if you have any refurbished that there could be a dif. NIC.

Beyond that perhaps some physical encouragement? With a hammer? Maybe some greased lighting?

just shots in the dark. Hope it helps or at least sparks an idea.

Jason

@badhonsoam
So this is the attempt from awhile back at getting Windows to boot:
fog pxe/iPxe boot win 7 wimboot CD/DVD missing issue
You must use WinPE to boot. You can download it here.
Or just google/search windows ADK.
Once you have that installed you can make the WinPE boot ISO.
Also once you have that, you can copy any normal Win install to a share and use its setup. The instructions(and what we found) should all be in the original link I posted.
I think @george1421 may have a better/cleaner tutorial somewhere. Or someone did at one time. But this should get you in the right directon.

@george1421
You’re are welcome to use anything of mine. In fact I think you helped get the windows boot working awhile back. I’ve borrowed and tweaked just a bit from sources here at Fog anyway myself.

I have to much going on right now to test what I posted but I know it has worked. My current location has a bare bones setup just for deploying an image. I haven’t had time to setup the advanced menu items(well the actual files anyway).

In my Fog Config, Advanced Menu settings I have these line items for calling windows install and Linux boot…

:Win7pex64
initrd http://${fog-ip}/opt/Win7/ISO/winpe_amd64.iso
#prompt
chain memdisk iso raw || goto MENU
boot

:mint18_64
kernel http://${fog-ip}/opt/mint/18.1-cinnamon-64bit/casper/vmlinuz
initrd http://${fog-ip}/opt/mint/18.1-cinnamon-64bit/casper/initrd.lz
imgargs vmlinuz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}/var/www/html/opt/mint/18.1-cinnamon-64bit/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=us mirror/country=US
boot || goto failed
goto start

Obviously you will need to setup matching locations with proper rights. There are articles, threads, etc that can help. I think Tom already listed some.
getting rights and NFS all to cooperate was the trickiest part.

For Windows you MUST use the WinPE version. I tried to use a standard USB bootable and did not work. Had to be PE.

For linux I just used a version of mint. Had to use it extracted. As in not the iso and link to the boot files.

Now there were some changes to Apache(at least Fog’s implementation) as well that may affect the path(s) you can use. To be honest I haven’t tried this in awhile. You may have to tweak your paths to work or Apache settings.

Jason

@computercolin
Just my $.02 worth… IF you are forcing a network boot it may loop as well. At least on our DELLs if you hit F3 to FORCE network boot and then try to boot to HDD/SSD it wont find it. Now this is also using DNSMASQ to send a boot menu and options. Not a straight DHCP.

If allowed to pick up network boot automatically(even at first option) it works normally.

This is all before fog menu comes up, purely the pxe/ipxe boot process.

Jason

In the reports section there is an imaging log. Go to report management and on left side column there is Imaging Log. It should show all the relevant data and you can even export it to csv or pdf.

It’s possible you need a current version. I am running Fog 1.4.0.

Jason

@BedCruncher @wciws
I would agree. i use the setupcomplete.cmd to create/activate logins and check installs.
You will likely need to create the scripts directory though. I believe I have another script run from the sysprep.xml file though that does some installs, adds to domain and registers/activates windows. I don’t rem. where in the file though.

@wciws
Ugh. I feel your pain. I hate how picky and unforgiving sysprep is. I have had quirks with copyprofile. If you used a diffrent profile other than administrator it could be “confused” so to speak. Since your error mentions localuser that is where I’d start. Remove the copyprofile line(s) or set it to false and test.

Also if you have made any changes to backgrounds, or anything that would have a path in your <sysprep>.xml file double check that the paths are correct.

Double check any post scripts you may have as well, although If the path to them is correct the error would be different I would think.

Make sure you don’t have any Antivirus services running or the3 Fog Client service. These services will bomb out the sysprep and cause it to crash. For instance we use Avast and just to be safe Avast is uninstalled just before prepping. I have a script that re-installs it after the fact. I don’t use the Fog Client but it is the same way. You have to stop the services or install it later.

Sorry I can’t give more specifics. But maybe can get you in the right direction.

Jason Bradley

@zln1996
That’s awesome! Glad to hear you got it working. I figured that directory under run would have been created automatically when starting the process. How interesting. Good job and glad all is intact. Glad we were able to get you in the right direction.

Jason

@zln1996
Wow. I’m not really sure. I would hate to think you’d have to go that extreme. Maybe someone else knows better than I.

However…
Did it ask you for a password during re-install? I will say that mine did but the login still didn’t work. Root was still missing I still had to use the --skip-grant-tables to get in. There is also a network related switch/option but I don’t know for sure what that does. Maybe skips issues if it denies login from localhost?
I think its --skip-networking. You can try that. I may have used both now that I think about it. I’ve slept a couple of times since then though. LOL

The only other thing I could think(if you didn’t) is to verify that the config files are gone from /etc/mysql when re-installing.

The next thing would be purely experimental… But there is a mariadb that is supposed to be a drop in replacement for mysql. You could try installing that and see if that fixes it. But I have not tried this.

I’m sorry I can’t be of more help.

@ttrammell
It looks like something similar when I had changed the IP and didn’t finish configuring everything. I had left out checking and configuring the Storage group/nodes.
If you have changed your IP(or maybe even Server name) try following these instructions:
https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
The key part I missed(becasue I didn’t really use storage nodes) was:

Update the IP address for the storage node on the FOG system where you changed the IP address - Web Interface -> Storage Management
Make sure you actually click the node and check the IP setting.

that line in the bandwith.php file points to a location in /sys/class/net/<net_adapter_name>/operstate

I’m not sure if CentOS is diferent but my adapter name is eth0 so look for that in place of adapter name.
Im not sure if you can simply recreate it it if it doesn’t exist. It simply appears to display whether or not your adapter is up or not.

I also found this article but refers more to the fog client install.
https://forums.fogproject.org/topic/5926/change-fog-server-name

Hope that helps,
Jason

@zln1996
Also you are quite welcome. I just hope its useful info. These guys on here have helped me quite a bit to keep things running and setup stuff. So I try to help or add my $.02 worth.

I dunno they might would like for me to stop.

@zln1996
I forgot to mention you can use

ps -ef | grep mysql

to find other potential instances of mysql running.

as far as removal goes…

sudo apt-get remove --purge mysql-server mysql-client mysql-common
sudo apt-get autoremove
sudo apt-get autoclean

then to re-install…

sudo apt-get update
sudo apt-get install mysql-server mysql-client mysql-common

If you don’t have a .sql backup you can try backing up these folders:
/etc/mysql and /var/lib/mysql
it looks like, at least on mine, that the data is in /var/lib/mysql. It has matching info for my databases anyway.

Using --purge will certainly get rid of config files. Maybe it leaves the data though?

If this is a full blown live production server I might wait til i hear back from one of the Fog pros. While I use mine regularly it is not mission critical so to speak. I also had backups I could use. I was also prepared that I would have to just manually re-enter the image info as the files would still be there.
My killer would have been losing my advanced pxe scripts lol.

@zln1996
hmmm… Maybe the server isn’t stopping all the way. I think you can try:

killall mysqld

Mine gave me this error as well but don’t rem. what all I did now.

You may also need to check your mysql config file “my.cnf”.
should be located in /etc/mysql/my.cnf
while I didn’t find them here, you can also check:
/etc/my.cnf
/var/lib/mysql/my.cnf

Make sure any IPs match your server and check where it says the .sock file is supposed to be. There is also a bind statement listed, but from what I read(and as was in my file) it should be commented out.
As I checked mine just now I don’t see any IPs or names other than at the bind-address which is commented out.

You could also try just making the .sock file:

touch /var/run/mysqld/myssqld.sock

keep in mind when making these changes you will need to use sudo or run as root(sudo -i).

Check your error.log file in /var/log/mysql/error.log
It may have some more info.
also: /var/log/mysql.err and /var/log/mysql.log
although for me the last two were empty.

Now I will tell you that I eventually re-installed mysql but I would use that as a last resort. My DB data stayed intact(as far as fog info goes anyway) but I may have been lucky.

after re-installing I used the steps provided previously to re-add the root user and it’s rights. I didn’t realize the root user was gone til after the re-install so I figure I may not have had to do that.

@zln1996
I had troubles this past week after updating as well. My issues I’m sure was due to my own clumsyness. We had a fire drill and in my haste I kicked the power to the station during fog update. The DB was not in good shape after and had similar problems. I am by no means a MySQL/DB pro so please use caution with my assistance.

So what I found was to stop mysql service and use this command to get into the DB…

sudo mysqld --skip-grant-tables

Then in another terminal run:

mysql
use mysql

After trying a bunch of other things(table repairs and such) I realized the root account was missing(as were others).
You can use this to check existance and should show rights assigned.

select * from user where User='root';

I can’t find the page that helped me most but I think next is:

FLUSH PRIVILEGES
#if root doesnt exist...
insert into user (Host, User, Password) values ('localhost','root','');

#IF/after root exists...
update user set Select_priv='Y',Insert_priv='Y',Update_priv='Y',Delete_priv='Y',Create_priv='Y',Drop_priv='Y',Reload_priv='Y',Shutdown_priv='Y',Process_priv='Y',File_priv='Y',Grant_priv='Y',References_priv='Y',Index_priv='Y',Alter_priv='Y',Show_db_priv='Y',Super_priv='Y',Create_tmp_table_priv='Y',Lock_tables_priv='Y',Execute_priv='Y',Repl_slave_priv='Y',Repl_client_priv='Y',Create_view_priv='Y',Show_view_priv='Y',Create_routine_priv='Y',Alter_routine_priv='Y',Create_user_priv='Y' where user='root';

#
grant all privileges on *.* to 'root'@'%' with grant option;
grant all privileges on *.* to 'root'@'localhost' with grant option;

while I didnt use this site:http://www.helpfromfriend.com/featured/how-to-recreate-root-account-in-mysql/ initially ,
it does layout basically what i had to do.

you may need to add: IDENTIFIED WITH mysql_native_password BY ‘’ to the end of the GRANT statements. I think I had to.

If you want to check/repair tablesyou can check this site on how to:
http://www.thegeekstuff.com/2011/12/mysqlcheck

The experts here may over rule me but it helped me.

hopefully this helps you. Or at least someone.

Jason

From what I see(although I am a snapins novice) you were/are trying to run an .exe with msiexec. Msiexec should be used with .msi packages. I could be misinterpreting the logfile though. Also I have had issues when trying to repack .exe files into an .msi and the repacked/wrapped file not installing in the manner you described. Using AD software install, it would push/run but the .msi wouldn’t actually install. Since you don’t need to repack it, like Wayne mentioned, Try using a script to call the exe, or Office has a builtin .msi. In the list of folders for your office setup there should be a ‘version.WW’ folder(so enterprise.ww or maybe proplus.ww, etc.) that will have .msi and .xml files for configuration.

It looks like Wayne’s links also point to info on doing silent installs or setup options. In short you can call your officesetup.exe /admin and get to the config tool to create a .msp file to use with setup, although I haven’t tried that with the .msi version(just the .exe).

Just my $0.02 worth,
Jason

@Wayne-Workman
Thanks for clarification. I misread as well and got a bit excited. And now that I think about it, it may have been a 990 in my case not a 790. Honest mistake as they are sitting side by side and look the same.

Anyway, good to know that UEFI net boot isn’t required for getting a UEFI/GPT image.

thanks,
Jason

@sudburr
Im interested in this too. I have a 790 I was testing with back in Nov. George was helping but could only get it to work in non proxy mode(using dnsmasq). When proxy mode was used it wouldn’t uefi boot. I was going to get back to testing but other priorities arose.