Posts made by ChrisG

Before I start I know this is not a “supported setup”. I am attempting to make multiple nodes sharing one image folder. We have a VMWare server and have a completely empty host. I created an NFS Share one one server and made it 777 for 10.0.0.0/8 and exported it. I mounted it with my first node, entered it into the FOG GUI, and allowed it to replicate. This worked smoothly with no issues.

Upon trying to image my first machine from this node I get the following error:

• mount: 10.10.150.220:/images/ failed, reason given by server: Permission denied
  mount: mounting 10.10.150.220:/images/ on /images failed: Bad File Descriptor.

Has anyone tried this with success? Any ideas where to point me on getting this resolved?
Thank you in advance!

We leave the ip address field blank. The installer looks for fogserver by default. Regardless of the actual server name I put an A Host record in my dns server to point to fog. This has solved tons of problems for us.

In windows 7 I found this option. It is listed when you configure the properties of the NIC.
The only time we have gotten it to work in windows 7 is with the Magic packet box checked. However I have not tried the top box to turn off powersaving. This may be a fix also.

2008 R2

That may be the issue. Our AD domain was setup before I arrived here. He may have removed those rights. I’ll look into it.

Thanks!

You must do something different chad. We cannot successfully join the domain without netdom. It gives a trust relationship everytime.

Any time man. I know how much work it is starting out and getting used to some of the quarks.

I attached a zip file with it inside to my last post

This is a simple windows file that is used via the command line to join the domain and change the name. I copy mine to c:, c:\windows, and c:\windows\system32 You also have the fog service installed right? If so, You will need to restart the service for it to try again.

[url=“/_imported_xf_attachments/0/316_NetDom.zip?:”]NetDom.zip[/url]

1 - Have you tried adding netdom to the machine? That is what the FOG Service uses to join the machine to the domain and rename it.
2 - I will attach my xml to this post. This is actually the one I use for 64 bit as we are all 64 bit. It can easily be adjusted. You will also need to change the extension to .xml from .txt. I couldn’t upload a xml. We do not use fogprep on windows 7 images at all.

[url=“/_imported_xf_attachments/0/315_unattended.txt?:”]unattended.txt[/url]

I know this topic isn’t quite what you are looking for but it does explain alot about how fog works and what slows down the process. [url]http://fogproject.org/forum/threads/specs.3918/[/url]

Does anyone have a sample powershell script for installs?

I believe you have to turn on .net 3.0 so that it installs 2.0 in add remove windows features. I think most of Fog’s windows programs were built in .net 2 or 2.5. If you turn on the features for 3 it adds this backward compatibility.

Have you had any luck with Windows store apps in audit mode? I seem stuck.

Chad as a side note to your statement. I have NetBios blocked on our domain and it still works.

Do you have the username as domain\user? or just user?

Chad - I changed my password so that it simulated a correct one but was not mine.

I have a similar setup as SNT. We are deploying windows 8 in mass now and have no issues. The only thing I can see is that you have to install .netfx3 Will this be changed in .33?

Have you tried changing the hard drive type in the bios to legacy?

Putting netdom in those locations will fix one issue. Once you get fogcrypt to work that should fix the remainder and they should rename after that. Can you post the output of the file? The password should look something like this f3815ea656cbfdcb06829ce62067791d

From what I understand if you do not use the 100Mb partition single disk single partition does not work. As far as changing the drive letter I have never tried it however google brought up this result [url]http://thebackroomtech.com/2009/10/15/howto-automatically-change-the-cd-rom-drive-letter-after-running-sysprep/[/url] We do not fog prep here only sysprep. My understanding is that it is not needed in windows 7.