It's not clear to me from reading the documentation if I must update the clients, or whether I can just update the head node and compute nodes.
Does anyone have any experience of this? I don't want to update my cluster and find that my customers can no longer connect.
I have a network infrastructure of Windows XP clients (a mix of XP and 64-bit XP), that are accessing a network share on a Windows 2008 R2 server. Whenever users type the address of a folder into the address bar of Windows Explorer it's as snappy at determining the contents of the current folder and presenting them to you in the address bar as if you're working on a local drive.
But if you open one of the subfolders users get the animated red torch and 'Searching for items...' dialog, typically for 45 seconds.
Similarly when using the open folder dialog to try and select a subfolder on this share it takes, on average, 45 seconds for the dialog to expand each node and show the subfolders of each node.
Also, while the Explorer instance accsesing the network share is running slowly users notice that the performance of all other Explorer windows suffers. So while Explorer is searching for files on the network share they can't switch to another task and navigate around their local drive using Explorer because it's now as slow as a dead dog at accessing anything.
Are there any settings we can change which will improve the performance accessing network shares?
I'm having trouble setting up the trust relationship between a Windows Server 2003 and a Windows Server 2008 AD.
Domain a is Windows Server 2003 Forest functional level.
Domain b is a Windows Server 2008 Forest functional level.
I can set up the incoming side of the trust relationship on domain "a" so that it trusts domain "b".
Try as I might on domain "b" I can't set up the outgoing side of the trust relationship to domain "a".
The GUI interface gives an unhelpful 'The request is not supported'.
I'm not sure netdom is being more or less helpful as it refers me to FilterSIDs
netdom trust /add b /uo:b\admin /po:* /d:a /ud:a\admin /pd:* /oneside:trusting To improve the security of this external trust, security identifier (SID) filtering is enabled, however, if users have been migrated to the trusted domain and their SID histories have been preserved, you may choose to turn off this feature. For more information about SID filtering and how to turn it off, see the help for netdom trust /FilterSids or see Help and Support. The request is not supported. The command failed to complete succesfully.
I say 'less helpful' because Windows Server 2008 doesn't support the /FilterSIDs option.
How can we force creation of this trust?
Edit: Just to clarify I've checked that the [Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options] "Network access: Allow anonymous SID/Name translation” is enabled on both sides of the trust as per http://social.technet.microsoft.com/Forums/en/winserverDS/thread/cc61fc25-3569-4413-bbfd-92390eb31118
Following the steps in the Windows Deployment Services getting started guide to create bootable media. After running Copype.cmd ia64 c:\winpe there is no equivalent of etfsboot.com in the c:\winpe\iso\boot\ folder.
So as per http://technet.microsoft.com/en-us/library/cc749311%28WS.10%29.aspx I use efisys.bin.
I've then burnt the ISO to DVD using infrarecorder, but the target box (HP Z600/Intel Xeon) insists on attempting to boot that it is a non-system disc.
Any hints or tips appreciated.
I've got a HPC 2008 cluster of HP Z600 workstatsions, and though my head node can add them to the cluster (using node.xml files), and can reboot them, when the Z600 powers on the PXE attempt just times out.
When the cluster node boots up the head node reports that it is 'sending PXE command to boot node to WINPE (expected boot time: 5-15 minutes)'.
Meanwhile the cluster node goes into PXE, but sits twiddling it's timer before reporting a PXE-M0f then finally a non-system disk error.
HP UNDI PXE-2.1 V11.4.0 HP Base Code PXE-2.1 v1.1.0
Any advice on forcing these Z600s to take their medicine gratefully received.
I'm working in an environment where students need to access a subfolder on D:\ for (VMWare) virtual machines. Obviously they need full permissions to this folder to be able to run the VM, but shouldn't be able to write anywhere else on D:.