Posts made by Raff

Never really checked it but I thought windows 7 sysprep removes them.

Leave all modules turned on at the client. Turn them off globally from web console.

By default the client looks for DNS record fogserver if servername is left blank. If you create an A record for fogserver it will find it.

You could repackage the MSI with the servername with something like qwerty.msi

The windows fog client no longer registers a host, it was removed a few versions ago. You need to import host on web console or register through pxe menu.

The only thing I can think of then is that maybe you don’t have the generic KMS key on your windows 8 host. Try changing it:-

[url]http://technet.microsoft.com/en-us/library/jj612867.aspx[/url]

I see. We were already running KMS for windows 7 /office 2010, just updated KMS for Windows 8 and office 2013 and didn’t have to worry about the count (already reached in Windows 7).

An update to the schema scares admins.

To be honest, I don’t understand what you mean by AD activation. Its only MAK or KMS? We use KMS successfully with Windows 8.

AD activation new in windows 8?

2008 R2 and FOG 0.29 here

If you have DHCP running you can export the MAC addresses from there.

No need for netdom, make sure the user that you use has delegated control to join/delete computers on the domain. Hopefully your not using the Domain Admin account. We use Domain\user for the username too or else there is an error.

You need to make sure windows 8 rearms. Remove skiprearm=1 from your unattend xml or rearm after imaging with a script to get an unique CMID (slmgr.vbs /rearm)

With Multicast all the processing is happening at the server e.g uncompressing the image. Someone once did a guide on how to modify this so that the uncompressing of the image is handled by the client on Multicast, I think he also modified it to use pigz rather than gzip to take advantage of multicore processors on client. We couldn’t get it work properly on our network.

I think that post might be on the old forum.

Try running it from an elevated command prompt or try another computer. Running version 0.29, not had that issue.

[url]http://fogproject.org/wiki/index.php?title=Plugins:_Capone[/url]

You still don’t understand.

You can use your FOG server 172.19.102.17, you have mounted your NAS storage on it? You just use /images2 on 172.19.102.17 rather than the /images.

Your too busy trying to fix the freespace issue and not seeing the bigger picture. Have you tried deploying images yet? Other things are not going work too because NAS box is not a FOG storage Node!

What FOG services are running on 172.19.106.6? None, so how can you define it as a fog storage node?

I’ll try an be more clear this time. You can not define your NAS box as a FOG Storage node, its not. Think of your NAS box as a bunch of disks that many operating systems can share. The FOG server that’s mounting disks from the NAS box is the FOG storage Node.

Another OS example might help:-

If you had a microsoft server running IIS7 for a website and its storage was mounted from your NAS box. Would you point your browser to 172.19.106.6 to view the website or the microsoft server?

The application services are on your FOG server not the NAS box. Your NAS is just a bunch of disks that can be accessed from the network!.

Yes, Define them for any scope that has computers or your clients don’t know where to look for the boot server (Fog server). Make sure that these options are not defined for other systems, IP phones sometimes use options 66 & 67.

Ideally if you had IP phones that use options 66 & 67 they would be on a different DHCP scope than your computers

So what cant you do? Detect means nothing. Can you see fog menu on clients? Have you defined options 66 & 67 for the other DHCP Scopes?

Looks correct to me.

Your NAS box is not a true FOG storage node (FOG software not installed) i.e path /var/www/fog/status/freespace.php does exist on your NAS box 172.19.102.6.

If it was a normal Linux box you would modify /var/www/fog/status/freespace.php on 172.19.102.6
[CODE]define( “SPACE_DEFAULT_STORAGE”, “/images2/” );
[/CODE]

Same node can not have more than one mount point for images.

Can you ping your clients on other vlans from 10.10.0.150?