Posts made by Tywyn

@x23piracy: Yes it does …

Hi everone,

running fog 1.5.2 an encountered a thing, that never happend before to me:
I put a computer in an installgroup “Inst” and associated the image “M2_Win7_Off2016_Seminar - (22)” to that group.

When running the deploy task fog tries to deploy another image “Fuji_P556_2_E85_Win10_64_Off2013 - (2)”:

Any ideas?

Thanx in advance
Rainer

EDIT: When I associate the image with the plain host and create a deploy task, the correct image is used.

Hi @Wayne-Workman,

I cannot see an LVM being in operation:

$ df | grep sda
/dev/sda2      479565648 10727584 449163292   3% /

$ sudo vgdisplay
$

I tried to capture another ubuntu 18.04 machine with fog 1.5.2 and it worked though. Maybe it ia an issue with 1.4.4

Thanx anyway

Hi there,

I twice tried to capture a machine with a fresh installation of Ubuntu 18.04 with fog 1.4.4. and in both cases I got an error during the resize of the filesystem. See picture:

Result was in both cases, that the client-OS did not come up anymore.
I do not know, whether this error also comes up with fog > 1.4.4

Regards
Rainer

Thanks for your advice. Will try on monday.

Hi everybody,

just setting up a new fog-server (1.5.2). Was testing a deploy task with a machine and it failed, because the client could not mount the images directory.
The fog-server mounts the images-directory from a NAS via nfs.

Obviously reexport is not possible:

# exportfs -a
exportfs: /images/dev does not support NFS export
exportfs: /images does not support NFS export

Any idea, what I can do?
Thanx, Rainer

So, now I did some tests. With all changes I everytime restarted the FOGMulticastManager.

ens33 remained the same, having ip 10.203.8.31

1. Changed enp3s1 to 10.203.80.4 -> Multicast workes
2. Deactived enp3s1 -> Multicast workes
3. Changed enp3s1 to 192.168.100.1 (same config, which did not work before) -> Multicast workes
4. Changed enp3s1 to 10.203.80.4 -> Multicast workes

So, in all 4 cases Multicast works now. Very strange.
I would consider the case closed for me, but it is anyway strange.

Maybe someone could try to have same scenario as I had to maybe reproduce the thing. In brief:

Version 1.4.4
Setup 2 NIC with IP-addresses A and B
define IP Address A for fog-server -> multicast worked
Change fog-server address to B -> multicast stopped working
Chance IP A into IP C -> multicast works again.

Thank you for you help, gentlemen!

@Sebastian-Roth
It is a debian 9.

@sebastian-roth said in Multicast does not work anymore:

/sbin/ifconfig -a | awk -F’[ /:]+’ ‘/(cast)/ {print $4}’

# /sbin/ip -4 addr | awk -F'[ /]+' '/global/ {print $3}'
10.203.8.31
192.168.100.1

Yes, the old interface is still running. From the beginning we have had both ip-addresses. I just switched fog from one interface to the other one.

The other command you postet just output twice “netmask”. So here is the full ifconfig.

# /sbin/ifconfig -a 
enp3s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.100.1  netmask 255.255.255.0  broadcast 192.168.100.255
        inet6 fe80::a61b:9cdd:69ce:1d4b  prefixlen 64  scopeid 0x20<link>
        ether 98:de:d0:1b:bd:d5  txqueuelen 1000  (Ethernet)
        RX packets 83  bytes 7640 (7.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 180  bytes 17066 (16.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.203.8.31  netmask 255.255.248.0  broadcast 10.203.15.255
        inet6 fd00::4a79:ee8:ead6:2c9c  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::78d3:810d:4c36:e801  prefixlen 64  scopeid 0x20<link>
        ether 00:25:11:5e:6a:86  txqueuelen 1000  (Ethernet)
        RX packets 57921  bytes 7461829 (7.1 MiB)
        RX errors 0  dropped 13  overruns 0  frame 0
        TX packets 6536  bytes 1220003 (1.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Lokale Schleife)
        RX packets 1156  bytes 162929 (159.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1156  bytes 162929 (159.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Ok, setup a second linux machine and did the tests, that are described here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast

This test worked (I received on the second machine the fogsettings-file).

Still the normal deploy via multicast stopps at the clonepart-screen.

@wayne-workman

Will run through this troubleshooting page. Have to install a second linux first

@wayne-workman
Wayne, I was not aware of that.
Does that mean, that SYSTEM does not have access to those commands (like New-LocalUser) at all?

@Sebastian-Roth : Hiya,

ens33 is correct and the ip 10.203.8.31 is also correct.
Running version 1.4.4, yes.

2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:25:11:5e:6a:86 brd ff:ff:ff:ff:ff:ff
    inet 10.203.8.31/21 brd 10.203.15.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fd00::4a79:ee8:ead6:2c9c/64 scope global noprefixroute dynamic 
       valid_lft 7110sec preferred_lft 3510sec
    inet6 fe80::78d3:810d:4c36:e801/64 scope link 
       valid_lft forever preferred_lft forever

mutlicast.log (Guess here is the error. Have had 192.168.100.1 before as IP):

== Released under GPL Version 3 ==
==================================


[11-29-17 2:00:45 pm] Interface Ready with IP Address: 127.0.0.1
[11-29-17 2:00:45 pm] Interface Ready with IP Address: 127.0.1.1
[11-29-17 2:00:45 pm] Interface Ready with IP Address: 192.168.100.1
[11-29-17 2:00:45 pm]  * Starting MulticastManager Service
[11-29-17 2:00:45 pm]  * Checking for new items every 10 seconds
[11-29-17 2:00:45 pm]  * Starting service loop
[11-29-17 2:00:45 pm]  | This is not the master node
[11-29-17 2:00:55 pm]  | This is not the master node
[11-29-17 2:01:05 pm]  | This is not the master node
[11-29-17 2:01:15 pm]  | This is not the master node
[11-29-17 2:01:25 pm]  | This is not the master node
[11-29-17 2:01:35 pm]  | This is not the master node

Where could be this 192.168.100.1 still configured?
Thanx for your help

PS: Will be out of office till next monday. So do not wonder, why I do not reply

@quazz said in Snapin Powershell 32/64 bit issue?:

%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe

Tried it, but strangely it does not find the New-LocalUser command. Here is the output, when I invoke it as a snapin (script works fine when invoked in the Powershell ISE on the machine itself:

**********************
Start der Windows PowerShell-Aufzeichnung
Startzeit: 20171130095507
Benutzername: C3-RAUM327\SYSTEM
RunAs-Benutzer: C3-RAUM327\SYSTEM
Computer: C3-R327DOZENT (Microsoft Windows NT 10.0.14393.0)
Hostanwendung: C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -NoProfile -File C:\Program Files (x86)\FOG\tmp\C3-327_Install.ps1
Prozess-ID: 7052
PSVersion: 5.1.14393.1715
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.14393.1715
BuildVersion: 10.0.14393.1715
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Die Aufzeichnung wurde gestartet. Die Ausgabedatei ist "C:\output.txt".
Überprüfe Voraussetzungen.
C:\Windows\system32\cscript.exe...
   -> Gefunden
c:\Programme\Microsoft Office\Office16\ospp.vbs...
   -> Gefunden
C:\Windows\system32\slmgr.vbs...
   -> Gefunden
Starte Modifikationen
Erstelle neuen Benutzer C3-R327DOZENT...
New-LocalUser : Die Benennung "New-LocalUser" wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder 
eines ausführbaren Programms erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt ist (sofern 
enthalten), und wiederholen Sie den Vorgang.
In C:\Program Files (x86)\FOG\tmp\C3-327_Install.ps1:142 Zeichen:5
+     New-LocalUser $UserName -Password $UserPasswordEnc -AccountNeverE ...
+     ~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (New-LocalUser:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
New-LocalUser : Die Benennung "New-LocalUser" wurde nicht als Name eines
Cmdlet, einer Funktion, einer Skriptdatei oder eines ausführbaren Programms
erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt
ist (sofern enthalten), und wiederholen Sie den Vorgang.
In C:\Program Files (x86)\FOG\tmp\C3-327_Install.ps1:142 Zeichen:5
+     New-LocalUser $UserName -Password $UserPasswordEnc -AccountNeverE ...
+     ~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (New-LocalUser:String) [], Comma
   ndNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

@Sebastian-Roth Good morning. Yes, this has worked and yes, there was a change in the IP-address quite a while ago. And it worked also after the change in the ip. I am not aware that I changed anything inbetween.

Hi there,

we are setting several things via powershell snapin (IP-Adress, workgroup, adding a new user). Some things work, others (e.g. adding users ) do not.

When I start the script locally on a machine with the powershell ISE 64 bit version everything works fine. When I start the same script with the Powershell ISE (X86), I get an error message, that the command New-LocalUser
is not part of a commandlet or function.

So, knowing, that some parts of the script are being processed when I let it run as a snapin from the fog-gui, but others are not (the addition of a new user) makes me wonder, whether snapins are being invokes with the 32-bit Version of Powershell, where the New-LocalUser is not available (for what reason ever).

How do I explicitely invoke the 64 bit version?

At the moment the call looks like this

powershell.exe -ExecutionPolicy Bypass -NoProfile -File C3-327_Install.ps1 

@Sebastian-Roth First tried to restart the FOGMulticastManager (then the logfile said, that it is already running?) and then I restartet the whole server a couple of times.

Hi there,

trying to deploy images to 2 machines via multicast, but it does not start. It keeps stopping at the Partclone-page.

Already cleared the DB with

TRUNCATE TABLE multicastSessions; 
TRUNCATE TABLE multicastSessionsAssoc; 
DELETE FROM tasks WHERE taskTypeId=8;

but this did not help.

/opt/fog/log/multicast.log says This is not the master node, but I have only one node installed.

Any ideas?

@x23piracy said in [Windows (Powershell) / Username=Computername]

@Tywyn like @Avaryan said why not use unattend.xml to create local users?

Having a Powershell-script, that does more, for example, set ip-addresses, active office/windows, sets the correct time, etc.

AND: I have no idea how to use unattend.xml

@avaryan said in Windows (Powershell) / Username=Computername:

Worked for me when I ran it locally on a Windows 10 Enterprise x64 computer. Will run as snapin soon to test.

Here is my code:

$Hostname = (Get-WmiObject -Class Win32_ComputerSystem).Name
$Password = "password" | ConvertTo-SecureString -AsPlainText -Force
New-LocalUser -Name $Hostname -Password $Password -Description "Local user." | Add-LocalGroupMember -Group "Users"

edit: Did not work when ran as a FOG snapin.

This code worked for me as well now.
Interesstingly, when I have the Add-LocalGroupMember in a separate line, it does not work.

This is what I tried (did not work):

New-LocalUser $UserName -Password $UserPasswordEnc 
Add-LocalGroupMember -Group "Benutzer" -Member $UserName 

Thank you gentlemen!