Chad

The registration process just creates a web URL with parameters such as mac address and hostname in it, so it shouldn't be too hard to script something. Or you could just hit the DB directly which would probably be my preferred option! Incidently, if you use OCS inventory, I wrote a plugin which will import your hosts directly from it into FOG. The auto-register functionality was removed (so I understand) as laptops connected wirelessly would register their wifi mac as the "primary" mac address, which likely wouldn't be the same mac used when they're imaged.

Also used it for years - more so in browser address bars than office, where I find it the easiest/quickest way to select the entire address line (after falling in the 15 click trap mentioned above and clicking too quickly past the initial click which selects all anyway...

Citrix have released new versions of both XenApp and XenDesktop. Issues fixed in XenApp 6.5: CTX130371 - Issues Fixed in Citrix XenApp 6.5 for Windows Server 2008 R2 - Citrix Knowledge Center Issues fixed in XenDesktop 5.5: CTX130369 - Citrix XenDesktop 5.5 - Issues Fixed in This Release - Citrix Knowledge Center However, it doesn't appear that you can upgrade from a previous version - you need to do a clean install followed by a migration: Installing and Configuring XenApp - Citrix eDocs Chad

Hi FatBoy, You can certainly create a CName (DNS Alias) for the server name to something more meaningful, but users would still have to type http://eclipse:81 Assuming you're using an MS IIS Web server, what you'd also need to do is configure the IIS server to look out for your new preferred name and forward the request to the appropriate hosted site. You can do this with a feature called "host headers". Have a search for that relating to your version of IIS and you should find what you need. Chad

We have .net 1.1, 2.0, 3.0, 3.5 and 4 on our image and I've not had any problems in joining the domain (FOG v0.31) I've recently patched FOG with a mod from the site which modifies the sysprep file immediately after imaging. This populates the correct hostname and the domain join instructions in the sysprep file, which means that the PC has the correct name and joins the domain without the need for the usual additional 2 reboots. As a start, I would try updating the FOG client on your image, as it looks like you're using an old (netdom required) version. Note that the client auto-register was removed about the same time as the dependency on netdom, so be bear this in mind if you need this feature.

I think 2008R2 provides more features (such as ABE enabled DFS) but I was unable to pursue such a setup as our forest functional level is too low at the moment. Hopefully setting the NTFS/share settings can be set centrally too and will propogate through to all replicas - definitely something I'd like to see, but I don't know if that's there either at the moment.

And also: The disadvantage to using a redirected folder is that you can modify it on the fly, and the changes are instant, rather than requiring the users to log off and back on. Scenario: using a DFS based shared desktop, somebody forgot to tie down the security permissions to read only on a new replica added into the DFS. It didn't take long for students to discover that, sometimes after logging in (i.e. when they were directed to that particular DFS replica), they had write access to the desktop. On saving an MP3 there, suddenly it appeared on an awful lot of desktops! Other files then followed with, let's say, some "creative" filenames which soon led to complaints. Luckily we were using push replication from the master share so they didn't do any permanent damage, and the "file owner" tab proved very useful Chad

Hi Modus, try fog/kernel/nameofkernel Don't forget the file names are case sensitive. Cheers, Chad

You can set proxy settings in your /etc/environment file on your Linux server (on Ubuntu anyway), along the lines of: http_proxy="http://username:password@host:port/" https_proxy="http://username:password@host:port/" Which works fine for most proxies. However, if your proxy uses NTLM authentication, rather than a username/password passed explicitly, then you'll need to use something like NTLMAPS to authenticate for you. You then set the host:port in the proxy settings to the IP:Port of the box running NTLMAPS (the port defaults to 5865)

For v0.30 there was a big update to the init.gz, moving to the use of "busybox" which made the PXE downloaded component much smaller (6Mb as opposed to about 30Mb for 0.29). However, many people reported very poor download/imaging performance with this version. One model of PC we use went from imaging in 5 mins to about 40mins with v0.30. Rolling back the init.gz file to that from 0.29 solves the problem, but at the expense of some of the improvements to upload speeds which were also added in 0.30. This doesn't really bother most people though as the download speed is the important factor. My advice would be stick with 0.29 for now if you're happy with how it performs. The interface rewrite in 0.31 is pretty major and there are fixes being reported and posted every day. I think it'll be a little while before it settles down. Chad

It's still very much php for the time being. The new release is a major interface revamp, I'm not sure what additions or improvements have been made. Looking at the FOG forums there's a lot of activity now on tweaking the code and bug fixing in general. I think I'll stick with 0.29 for now and wait and see what the general consensus is - I got very poor performance from 0.30 so would be interested to hear if that's been addressed in 0.31.

The voice of the Daleks too. I was watching the extras on Dr Who/Genesis of the Daleks just the other day and Roy has a few slots of "how to talk Dalek". Being done "live" and without the ring modulation, it sounded just like Zippy

Someone on the FOG forums reported that multicasting was broken with 0.30: Link Rather than reverting to 0.29, you should be able to substitute the init.gz from 0.29 into your /tftpboot/fog/images folder. I use a similar setup after experiencing a number of problems with 0.30, and the speed and other issues I was seeing went away. I don't use multicasting though so can't say for sure if it will fix the problem you're seeing.

btw, FOG doesn't give friendly test for some of the error codes, here's a few return values and what they mean: 5 = "Access is denied" 87 = "The parameter is incorrect" 110 = "The system cannot open the specified object" 1323 = "Unable to update the password" 1326 = "Logon failure: unknown username or bad password" 1355 = "The specified domain either does not exist or could not be contacted" 2224 = "The account already exists" 2691 = "The machine is already joined to the domain" 2692 = "The machine is not currently joined to a domain"

The hostname settings should be copied from the default ones when you tick the "jojn AD" box but I've seen FOG "remember" the old host settings before (they're actually stored against each host in one of the tables). Try blanking all the domain boxes against the host, then unticking thejoin domain, then save. Then if you tick join domain again it should pull through the global settings. I'd leave the username as domain\username (with domain in short name-only format) and make sure magic quotes is off in the php.ini file (restart apache if you make a change, assuming you're on a Linux box - don't know about the windows server setup)