@JJ-Fullmer Well done!! I wish I could upvote your post more that just +1.
Posts made by george1421
-
RE: executing batch file from snapin
-
RE: executing batch file from snapin
@Olduser If it was me, I would create some conditional tests.
Does the S: drive exist
Does the user account running this batch copy script have user rights to S:
Does the path S:\PAT exist
Does the file tdpunt.bat exist in the path S:\PAT
Does the C:\Temp path exist, if not then create it
Write the negative results of your tests to a log file in C:\Temp to help you figure out what went wrong. -
RE: "Content Encoding Error" after logon
@Ric41 A screen shot of the actual error, so the devs can see the placement and conditions of the error (with the understanding that you are using 1.2.0).
Browser used + version, client OS used when the error was generated. Is the language USA or some other format. Are other questions that come to mind.
-
RE: bzImage for new computer
@jrm What did you do differently to cause a kernel sync error?
-
RE: FOG 1.3.0 - SVN 6050 - "Please enter tftp server:"
@ttrammell If your fog server, dhcp server and pxe booting client are on the same subnet we can use tcpdump to capture the pxe booting process to see if you are getting another dhcp offer packet.
- Install tcpdump on the fog server
- start the tcpdump program with the following command
sudo tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011
- PXE boot the target computer to the error
- Press control-c on the tcpdump program
- Either review the pcap file with wireshark or post the pcap here and we can review it for you.
-
RE: FOG Client GUI reuse for Notification messages.
@davidedpg10 I did think of a way to do this while I was fixing my furnace today (don’t ask why).
You can use a snapin to deploy a batch file which calls the msg.exe command on the remote computer with the destination of the remote computer. Just have the batch file pick up the computer name from the environment variable or write a vbscript to do that. Since you are running msg,exe ON the target computer IT should know its own name.
-
RE: Unable to copy imatges to another node
@Malarky Yes that setup is correct.
Just by chance, have you rebooted your master node? (or at least restarted the FOG Replicator service)
-
RE: FOG Client GUI reuse for Notification messages.
I think I understand what you want, but this is not a native function of fog.
Just to be clear you want to display the name of the computer to the user or support tech. If I understand this correctly you can do this in three ways (not related to FOG).
-
You can instal BGInfo on the target computer, it will update/change the background on the desktop to contain the name of the computer, plus any other info you might need. https://technet.microsoft.com/en-us/sysinternals/bginfo.aspx
-
You can change/replace “Computer” in the start menu with the real name of the computer: https://www.experts-exchange.com/questions/28226225/Display-Computer-Name-in-Start-Menu-Win-7.html
-
Create a quick VBScript that pops up a window that displays the computer name. Just create a menu short cut that calls the vbscript.
-
-
RE: Unable to copy imatges to another node
This is a bit strange.
Just to be sure you installed the location plugin (not needed for your current test, but will be needed for your prod environment).
Then on your master fog server, you created a storage group (or used default) and then added both the master fog server (should have already been in the default group) and the storage node in the same storage group. Right?
-
RE: FOG 1.3.0 LDAP Plugins - AD mail attribute
I can say this is an interesting request, and I’m almost sure it won’t work because the ldap plugin will see the email address jondoe@domain.com and think its a AD style user name “jondoe@domain.com” and strip off the (at)domain.com part.
I can say we have never tested changing the “user nam attribute” (which I see we have a type-o name is missing the ‘e’)
Can we first confirm that you can login properly if you use the samaccount name? The first step is to ensure the ldap plugin is working correctly. Then we can look at why the email address is not.
-
RE: Cannot capture ThinStation PC image "No resizable partitions found (/bin/fog.upload)
While this is really off-point here, why are you running thinstation from a hard disk drive?
We will typically use a tiny usb drive (like sandisk cruzer fit) and pull the HD and disconnect the cdrom (if not needed) from systems. The other option is we will pxe boot into thinstation depending on the environment.
I’d have to look at the disk on devstation to see, but I think its ext3 or ext4 format so fog should capture it.
-
RE: snapin query resizing partitions
I can’t speak for snapins (don’t use them). But you should be able to bundle files with a snapin in addition to the vbscript code.
Looking at your vbscript code this line raised a question
Set oShellExec = oShell.Exec("cmd /c diskpart -s " & diskpartScript)
diskpart is an exe not a batch script, so the
cmd /c
is extra. I might suggestSet oShellExec = oShell.Exec("diskpart -s " & diskpartScript)
Also before fog supported resizeable disks I used a script similar. It was a simple added at the end of the setupcomplete.cmd batch file. I ran the diskpart command with the commands just as you have to expand the disks. It worked really well. But now the single disk resizeable option in fog works much better. Just a warning, you have to capture the image in that mode for it to work correctly on the target computer.
-
RE: bzImage for new computer
@Tom-Elliott Needing the 4.9.x linux kernel with the patch that Sebastian found? Its the same network adapter if I remember correctly. The system is getting to stage 3 of the booting process (FOS) and failing to get an ip address??
-
RE: Best way to deploy Windows?
What OS are you deploying and do you plan on installing the FOG client on every reference image? There are different ways to go about this depending on your end goal.
Since you are a “small IT shop” does this mean you are a computer repair shop or an IT group inside your company. The approach will be different based on if you will see these imaged computers on a daily basis.
-
RE: Fog "menu* won't show up on client (stuck after fog/service/bg.png ok)
Along with Tom’s request, what precisely do you have for dhcp option 67?
We did have an issue last summer where bg.png would download and then bzImage would freeze at a certain percentage of download.
Can we also get the details on that motherboard? Is the NIC, LOM or an add on card?
Does FOG image other hardware at your site OK, just this one is troubled?
-
RE: file download from network share via ps1 / bat snapin non functional
First let me explain that I don’t use fog snapins so this may be a bit off point.
But the FOG Client runs as SYSTEM (unless you changed the default). The SYSTEM account has no rights outside of the box that the FOG Client is running on. Even if another computer has a SYSTEM account, that account is different and not a domain account.
To make your script work, it must run as, or connect to the remote share as someone who has rights on the remote share. If it was me I’d use a command like.
net use t: \\server1\share1 /user:domain\bob
and then supply the password fordomain\bob
to connect to the remote share to retrieve the file.
Then when your done issue the commandnet use t: /delete
to remove the share. -
RE: FOG will not boot - "Failed to get an IP via DHCP!
@Sebastian-Roth Is there any chance that an older kernel will work here? I’m going to assume that both Mint and Kali are using older kernels that do work (which may not be a solid test since @Wirefall is not pxe booting either OS platforms).
-
RE: Error Booting Samsung Style S20
@Schuede said in Error Booting Samsung Style S20:
@Wayne-Workman @george1421 realy worked! many thanks!
What did you do/change to make it work for you?
-
RE: FOG will not boot - "Failed to get an IP via DHCP!
@Wirefall From within the FOG debug console (the same place where you entered the
ifconfig -a
command key inlspci -nn|grep etwork
We will be interested in a line that looks like this
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04)
More precisely the hex numbers (i.e. [8086:1502] ) in the square brackets. Those numbers identifies the nic controller.
-
RE: Error Booting Samsung Style S20
Is this a uefi or bios system?
Did you disable secure boot?
The error message is roughly about starting the bzImage on this computer
What precisely do you have for dhcp option 67? I’ve seen a similar error message when and older pxelinux.0 is used for some reason to pxe boot.
Are you running a dnsmasq server or just a dhcp server?