morganw

...but you would still be exposing the BIOS and the bootloader which would be unprotected, in addition to anything the computer was connected to while it was running (on the network and local media such as memory sticks). Also I presume that the thin version of Windows 7 needs patching like the fat version so eventually it would require maintenance and you would have to deploy a new image or get it to keep changes after a reboot. The price is right though.

See if you have a policy set for: Computer Configuration / Windows Settings / Security Settings / Local Policies / Security Options / Domain controller: LDAP server signing requirements I think that's the right one to look at anyway, it's been a while since I adjusted my own to allow Moodle authentication via LDAP.

Don't you have to allow unsigned LDAP requests for your DCs?

You might save money on anti-virus by not using a Windows base for the thin client, but then again you would probably get better RDP performance using the newer Windows RDP client, maybe better battery life too. You should probably pick based on the how these laptops will be used although personally I would look at Thinstation first and go from there.

When I implemented password policies I used this: Product Documentation | Specops Password Policy Basic It's free and as well as configuring the policies I believe you can also select a user and see which policies are applying. May be useful.

You could use the free version of Alike to backup one XenServer to another Windows server. You can pay them for a licence to back up multiple XenServers to the same Windows Server or you can just run two Windows servers for backups installing the free version of Alike on each one.

This should be possible by running a script with Apple Remote Desktop (or I think Apple Remote Desktop has a button labeled "Unix Command" that might just let you type commands in directly. You probably want something like: networksetup -setwebproxy "Built-in Ethernet" newproxy.domain.com 80 "Built-in Ethernet" is a network service which should apply to any wired connection networksetup -listallnetworkservices should list all network services, any other type of connection (like airport) will have a separate service that you need to specify the proxy details for as well.

There is a separate bug when pushing the AD settings through groups and I'm not aware it was fixed. Try with a new host and set the AD credentials directly on that host.

I'm pretty sure that when using sysprep the only supported switch is actually from ACPI uniprocessor to ACPI multiprocessor because I used to keep a uniprocessor machine around to build images on. www.vernalex.com has all the information you need and, as suggested earlier, the sysprep driver scanner from the same site is really all you need to make universal images. The most awkward part to get right is the sysprep mass storage section but that doesn't really require as much maintenance in the long term.

An administrator can export the mail in a mailbox (and previous mailbox states) and also setup monitoring on certain users. The easiest way is to use GAM.

If it's just the TFTP transfer at the start which is slow this can be caused by buggy PXE implementations on network interfaces. I've seen this type of behaviour using Dell Optiplex 760 machines, the transfers are slow and bursty and multiple machines connecting to the server seems to make it worse. I would retest with a PC that has a different network interface. This problem isn't FOG specific, downloading a WinPE image through WDS has the same slow down.

I believe that they don't provide an easy route for this because it would be abused by third party software that 'helpfully' populates your task with a set of icons you didn't want. I think you could manage these by copying them into the profile using some kind of scripting, but that's probably only useful for mandatory profiles. I've got some vbscript that will pin items to the start menu if they are present on the machine if that is any help. Using the start menu rather than the taskbar would be more in-line with what people are used to experiencing at home.

I think you will have to leave the domain first, then after the FOG service changes the hostname it should re-join AD on the next reboot. I think the old computer object will be left in AD so you will have to delete that, the new name should appear wherever you FOG settings specify it should (or if you haven't specified a place it should be in the computers container). If these are wired clients then I would just trigger the rebuilds remotely in groups over a weekend to avoid the need to leave the domain, or you can set staggered scheduled tasks based on FOG computer groups to do this for you.

Just to add more confusion - I only ever used single partition images, and had no problems with it.

That suggests you have a DHCP reservation on the router itself which would need to be removed first, but you'll probably want to find out what equipment it relates to first.

If the firewall on the server is up and you have no rules to allow "ICMP echo request" then you will get a time out. http://www.howtogeek.com/wp-content/uploads/2008/06/image62.png

Installing Office with WPKG is pretty quick if you are on a gigabit network. I just deployed using the original image from a Windows 7 DVD using MDT2010, installed the antivirus and WPKG-GP as part of the task sequence, then all other software was installed with WPKG.

I've done the same.

Advanced Installer has a freeware mode that will let you build simple packages.

For a VDI system you'll probably have to use the Citrix connector as I don't think it even comes with an RDP client. Expensive but it would probably work really well.

There are probably options to restrict connections by IP address or MAC address in the management software, always worth a look. It would seem logical on the initial setup to restrict connections to the initial servers you had. Or you could swap the connections with a working one to see if it's a switch issue or cabling issue, assuming the switch ports haven't been configured with any special settings.

I'll also add that in my experience using OSX 10.6 or 10.7 with Server 2008 R2 SMB shares causes massive performance issues. In the end we went back to doing everything over AFP again, initially on Apple hardware with a long term plan to try and test again with Netatalk. Also it's the only solution I know of to avoid issues with software like iPhoto that doesn't work with SMB home folders.

And are they all using the same type of license?

I would imagine it's because of authentication settings on the Dell unit. You'll probably need some kind of admin program to investigate the settings. It's probably worth checking that the firmware on it is the newest as well.

Is is that they cannot see the file they have saved or that the file they saved doesn't open correctly? A Logic project file references original audio and edits from the project folder, when you save to another location you should choose to create a new project folder. You can choose what the project folder includes (and also strip out unused audio). You might want to take a copy of any plugin presets and samples as part of the project folder if they aren't using network home folders (any presets or sampler instruments you make are stored in your home folder). If they are just doing "Save as" all you have is the actual project file and I doubt it would open properly if the project contains imported audio, the audio files won't be there to load back in. If the file actually isn't there then it could be a permissions issue on the Windows server.