So I just needs a little clarification on this. Does the HostnameChanger need to be enabled for the EarlyHostNameChanger name to take change. I didn’t think so because one is part of the FOG client, and the other happens while Linux is still handling everything. I ask because I made sure the Early HNC was enabled, and then disabled the HNC, and the machine name was technol blah blah. instead of what the fog gui shows. I just updated to the newest 79xx version (not at work, forgot what it is, but just upgraded about an hour ago)

Posts made by adukes40
-
Early HostnameChanger
-
RE: Drivers script
@george1421
Ok so:-
the ln command is the same as net use to windows. Except here it is ln -s <SP> <DP> where in windows it is net use x: \server\share<rest of path if needed>
-
Being mydrivers is a symbolic link, it doesn’t technically have a directory, just a location to point to.
3.the ls -la /tmp command shows the OptiPlex 790 having a space. Does this mean the folder on the server needs to have a space as well?
- If the link is there, and pointing to the correct location, what is casuing this to not pull the files from the server to the ntfs mount.
-
-
RE: Drivers script
@george1421 hmm, ok I think the tmp/mydrivers is throwing me off.
When you say ln -s <source path> <Dest path> It registers to me to mean ln -s “/images/Drivers/${driverver}/${machine}/${setarch}/” /ntfs/Drivers;
Now does that mean the x86 folder get moved, or the contents WITHIN the x86 get moved. Does /tmp/mydrivers part need to be done, or can it copy straight from the server to the /ntfs/Drivers
-
RE: Drivers script
Looks there, but says it’s not. And it shows up a different color. I don’t know if that is normal or not.
-
RE: Drivers script
[Wed Jun 01 root@fogclient /tmp]# osdiskpart=“/dev/sda2”;
[Wed Jun 01 root@fogclient /tmp]# driverver=“Win7”
[Wed Jun 01 root@fogclient /tmp]# osdiskpart=“/dev/sda2”;
[Wed Jun 01 root@fogclient /tmp]# driverver=“Win7”
[Wed Jun 01 root@fogclient /tmp]# mkdir /ntfs 2>/dev/null
[Wed Jun 01 root@fogclient /tmp]# mount.ntfs-3g “${osdiskpart}” /ntfs 2>/tmp/mntfail
[Wed Jun 01 root@fogclient /tmp]# mkdir /ntfs/Drivers 2>/dev/null
[Wed Jun 01 root@fogclient /tmp]# mkdir /ntfs/Drivers/TEST 2>/dev/null
[Wed Jun 01 root@fogclient /tmp]# cd /ntfs/Drivers/
[Wed Jun 01 root@fogclient /ntfs/Drivers]# dir
TEST machine.txt
[Wed Jun 01 root@fogclient /ntfs/Drivers]# nano machine.txt
-sh: nano: command not found
[Wed Jun 01 root@fogclient /ntfs/Drivers]# vi machine.txt
[Wed Jun 01 root@fogclient /ntfs/Drivers]# vi machine.txt
[Wed Jun 01 root@fogclient /ntfs/Drivers]# rm -f /tmp/mydrivers;
[Wed Jun 01 root@fogclient /ntfs/Drivers]# ln -s “/images/Drivers/${driverver}/${machine}/${setarch}/” /tmp/mydrivers;
[Wed Jun 01 root@fogclient /ntfs/Drivers]# if [ -d “/tmp/mydrivers” ]then
cp -r /tmp/mydrivers/* /ntfs/Drivers;
else
fi
-sh: syntax error near unexpected token `fi’Everything seems to go smoothly until the bottom. I was able to cd into the ntfs mount, and create and new folder called TEST, and view the machine.txt. Ihave tried with a space in the model name. no space. Here is the file structure as well: (they all have spaces in them currently, but I am working with the 790)
-
RE: Drivers script
@george1421 i finding something odd:
[Wed Jun 01 root@fogclient ~]#
[Wed Jun 01 root@fogclient ~]# machine=dmidecode -s system-product-name
;
[Wed Jun 01 root@fogclient ~]# ${machine}
-sh: OptiPlex: command not foundSo with the tick marks at the start and end of the command it doesn’t seem to resolve the rest, so then i added " marks instead and i got this:
[Wed Jun 01 root@fogclient ~]# machine=“dmidecode -s system-product-name”
[Wed Jun 01 root@fogclient ~]# ${machine}
OptiPlex 790then i tried to run the remove spaces and it didn’t appears to remove the space.
[Wed Jun 01 root@fogclient ~]# machine=“${machine%”${machine##*[![:space:]]}“}”;
[Wed Jun 01 root@fogclient ~]# ${machine}
OptiPlex 790
[Wed Jun 01 root@fogclient ~]#More so, why would the tick marks you have in your scirpt cause this, but quotes provide the output. If for some reason the ticks are giving a partial name, maybe thats why it can’t find the drivers, because it doesn’t populate the ln command correctly. Not sure why I am having a hard time with this. does this make sense?
Furthermore, looking at your script and Lee’s, the tick marks are there, which seems to me they should work, but I have no clue why they are for me.
-
RE: Drivers script
@george1421 I will try that. Also should the permissions be set to fog root or fog fog for the Drivers folder?
Currently looks like this:
-
RE: Drivers script
@george1421 I am thinking that line of code is what was doing it, along with my misunderstanding of what it was doing. I have spaces in my naming structure on the fog servers. I commented it out to see if that works for me.
more than likely my lack of knowledge causing me issues. I am testing now.
And without looking, i think Lee’s scripts also had that line in there. So that makes sense why that didn’t work either.
-
RE: Drivers script
@george1421 Sorry I am new with this scripting mess, but tell me if I am correct here:
this line"
machine=“${machine%”${machine##*[![:space:]]}“}”;
turns OptiPlex 780 into OptiPlex780 … doesn’t it
-
RE: Drivers script
@george1421 I just do not know where my disconnect is. I have a 790 I am testing this on. I picked that because I know Win7 does not have embedded nic drivers for it, so I know when it does not work. just lost on where its not working. It looks like it is mkdir Drivers, but isn’t copying the drivers over from the server. I do have all my files extracted from the Cabs. I looked in the registry and didn’t see where it updated the device path either. still only shows %systemroot%/inf
-
RE: Drivers script
@george1421 https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins/23
his Main post, and on page 2 you will see the driver script
-
RE: Drivers script
@george1421 did your postdownload look any different? There are some variations with your driverinstall that differs from his. I will piece this one together and see what I get.
Also Case is important correct? so instead of fixing my case with Win7 in the directory in FOG, I can just edit the win7 in your script to Win7 instead correct?
-
Drivers script
So I took Lee’s scripts and tried to make them work. I will post them here, can anyone tell me where it is going wrong.
Here is what I am doing with it. It is basically the script he posted, except a couple modifications.
The script to be called is fog.driverinstall and the path to the drivers on the fog server is /images/Drivers/Win7/<Model>/<arch>Attached are the scripts. 1_1464786939362_fog.postdownload 0_1464786939361_fog.driverinstall
-
RE: Storage Node installations
@Wayne-Workman This in latest release I take it? Should help with new nodes I plan to add within the next few weeks.
-
RE: Google Hangouts Q&A
@Wayne-Workman you can put me down again. As of right now I am free, but only time will tell.
-
RE: Git 7917: web root for new storage node
i typed
/fog
mine is working with that set
I think there was a request made to fill it in by default, then the sysadmin could change it if needed, but /fog is what my storage node is using
-
RE: Client reboot screen
This really is a way of saving me 2 minutes lol. but on the other side the reboot screen just allow a user to talk up and hit delay for 10 minutes. This could cause other issues, especially working in a school district
-
RE: Client reboot screen
@george1421 I’m down to try new ways of doing things. The client is calling the snap-ins and the snap-ins are PS scripts. I am aware the client can do some of things PS is doing, and I was going to explore those once I get everything stable to replace our current solution.
What other ways could this be obtained?
-
RE: Client reboot screen
the first 2 scripts handle machine naming, and a couple machine settings. the 2nd scripts handle ad join, and registering to zenworks, then deploying software bundles.
-
RE: Client reboot screen
@Joe-Schmitt Correct Joe, sysprep with 2 auto logons. 1st logon calls 2 snapins, 1 runs, then 2 runs, 2nd has the reboot command, machine reboots, auto logon again, runs a 3rd script with reboot install, then machine is ready with Ctrl Alt Delete logon ready.
would not having the service running interfere with those snapins kicking off after imaging?