@wayne-workman I see the area you’re referring to but wouldn’t that be the product key just for THAT particular one machine? The same key won’t activate every machine I pull that image to, correct?
Posts made by dpotesta50
-
RE: Question About Windows Licensing
-
Question About Windows Licensing
So I’ve got my new FOG server up and running and are about to make a fresh Windows 10 image for our corporate machines. We order all DELL laptops that come loaded with 10 Pro. The image I’m making will be based on that installed copy of Windows 10 with our software installed.
So, how does activation work? Obviously imaged machines should not/will not activate because the same key can’t be used multiple times so how do I get around/resolve that? -
RE: Fresh Install of Fog - Setup PXE Boot
@george1421
That list is so long I have to roll the scroll wheel about a dozen times to get to the bottom. -
RE: Fresh Install of Fog - Setup PXE Boot
@dpotesta50 It’s very very slow though. Changing from option to option within the FOG program takes a minute or so.
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 The dashboard is up and running. I can access it and all the options. I just tried to PXE boot a laptop to it, no server found.
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 Yes I ran “sudo ufw disable”
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 It shows "SELinux status: Disabled
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 I’m running on Ubuntu desktop, is this still required? (selinux permissions)
-
RE: Fresh Install of Fog - Setup PXE Boot
Got to the end of the installation where it updates the database schema. Site won’t open in Firefox. Just times out.
192.168.100.100/fog/management -
RE: Fresh Install of Fog - Setup PXE Boot
Got it!
Kinda dumb, change to adapter number “2”. -
RE: Fresh Install of Fog - Setup PXE Boot
This is really frustrating. Once I get wifi back up, FOG wants to bind to that NIC as it’s main. I don’t know the terminology it’s looking for when it asks if I want to change the default network adapter. If I say yes and enter the NIC’s name, it throws syntax error.
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 Ethernet is literally just plugged into a switch that goes to nothing. My intent was to use that to connect a test device to for PXE boot. (This is all running on a Dell optiplex desktop) Anytime I “connect” to one, the other disconnects.
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 Install failed. Not connected to wireless so the repository couldn’t be setup.
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 Do I need to add anything to “setup a router address for the DHCP server”?
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 Okay never mind now it does. Ubuntu is using ethernet as it’s standard adapter, Wireless is available. I took the check off to auto-connect to wireless when it’s available.
-
RE: Fresh Install of Fog - Setup PXE Boot
@dpotesta50 No that line (2) for the enp2s0 adapter does NOT show my static IP address of 192.168.100.100
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 Wiresless is getting DHCP from MS. Based on what you instruction I need to bind Fog to the ethernet which I gave a static 192.168.100.100.
-
RE: Fresh Install of Fog - Setup PXE Boot
@george1421 well since I’m not over the main network and those who are, are busy with other projects lets keep FOG handling the DHCP for the PXE clients.