saundersmatt

We are. You do now Matt

Indeed you do not need to use the full management server and the streaming server. Also, since you are installing on 2k8 you will need to install IIS with the specific features Windows Authentication, IIS6 Management Compatibility and IIS Management Script and Tools If you decide to go a full deployment then this may just save your bacon if you get any client related problems. Matt

You will need to install the sequencer onto a clean computer and follow the wizard to create virtualised applications. Failing that you can get some freeware apps from Instant Applications and import them into the management server. Matt

Who did you get those prices from? I was under the impression that datacentre was a few thousand per cpu licence. Matt

I've decided to publicly release this tool that i've been using internally for a few weeks. Feel free to ask any questions or request any features/updates. Linky Matt

Glad to hear it mate. What's the plan for the fully stacked chassis anyway? Sounds like you've got quite a lot of power at your disposal now. Matt

I think that access the the management interfaces of the modules is through the bladecentre backplane, via the management module, not through the external ports. Odd i know but would explain your quandry. Keep trying Matt

That looks about right (Your interface is slightly different to mine). I'm at a loss now pretty much. Are you able to connect to the network module web interfaces? Matt

Have you ensured that the "External ports" is set to enabled? It will have disabled them when you reset the management module. Matt

From here. Insert a paper clip into the pin hole on the back of the advanced management module. Push the paper clip in all the way and hold it for approximately 10 seconds. The advanced management module will reset and the fans will run at full speed, which is clearly audible. Remove the paper clip from the pin hole. Matt

It's got a built in web server. Should get an IP from DHCP but if you can't find it then you can connect to it from a machine as follows. The following topics describe how to connect a remote console to the management module to perform initial configuration of the BladeCenter unit. The management module has the following default network settings: IP address: 192.168.70.125 (primary management module) Subnet: 255.255.255.0 User ID: USERID (all capital letters) Password: PASSW0RD (note the number zero, not the letter O, in PASSW0RD) Matt

Okay, thanks so far. Have you plugged the blade centre management module into the network? Connect to that and go to: Monitors -> Hardware VPD, under I/O modules it will tell you the Manufacturer and Product Code of the modules (I'm betting they're Intel IXM5414E) Then I/O Module Tasks -> Configuration, give the network modules LAN ip addresses and see if they are pingable, and can connect to their web interfaces. For each module click go to the advanced configuration (from the chassis management module) and ensure that under advanced configuration ensure that "External management over all ports" is enabled Then I/O Module Tasks -> Admin/Power/Restart ensure that "external ports" are enabled for each module. Also connect to each Network Module, and ensure that each port is enabled (Admin Mode = Enable) Good Luck Matt

Right, wesley, you're talking absolute jibberish! Let's clarify a few point first. There is no such thing a a Blade Centre HS20. A Blade Centre with HS20 blades is what you mean, yes? How many blades? Are the all experienceing this problem? "The lights on the NICs at back of the machine light up and flash when connected" I assume you mean the network modules? What slots are they in? What make/model are the (Intel, Cisco and Nortel are common). If you configure 2 blade servers with local IP addresses can they ping eachother? I think I have an idea what your problem is, but you need to slow down and make me clear about what you're trying to do. Hope I can help Matt

From my understanding once you add a domain as a zone on your dns servers it becomes authoritative thusly you cannot pick and chose which subdomains you want it to answer for. You need to do as microdigit suggests and add all sub domains as exist on your public dns server. The fact that you have multiple sub domains that may or may not point to different servers should not matter. So long as the subdomain and ip are the same between both dns servers it is the web server that resolves what content should be returned. Matt

Sad, posting follow ups to my own posts I know. I have just tested the latest Broadcom NetXreme II drivers (and management tools) on server 2008 R2 beta, they appear so far to support nic teaming combined with hyper-v. I am not sure if this is entirely a driver fix, or increased compatability with 2008 R2. Tommorrow's plan is to test the new drivers on an existing 2008 machine in the live cluster and see what happens. Matt

If all you want is to have the Macs connect to their windows home directory, you don't even need a Mac Server. You can configure clients to authenticate windows users and mount their home directories. Matt

Being the owner of a mere 720p LCD, i would definately say that 1080i is a big improvement. I am so jealous every time I see good full HD sources on one. If you can afford £150 then go for it. You'll only kick yourself if you don't. Matt

I knew I'd solve it as soon as I posted here! It does "just work", providing that you use the boot.wim from a vista dvd, rather than server 2008. Matt

Right, I'm trying to use Virtual PC 2007 to create some basic XP images to capture and deploy with WDS. I'm familiar with the entire boot/capture image + drivers + sysprep routine so theoretically I should have this working by now. The problem I'm having is that I cannot get my boot images to detect the network card. I've tried adding custom drivers, some random ones from the virtual PC folder and Intel 21440 drivers from the intel site. Neither of these work. Every guide i've seen seems to imply that it "just works" and shouldn't need custom drivers adding. Has anybody managed to get this working? Matt

Rolfea, you need to dig out your OS X server disk, install the server tools onto a workstation with the updated office. Then run workgroup manager on said workstation and add office as an allowed application. Matt.

Try restarting the full server. It's a really stupid .net related error message that one. Get it quite often on some of our 2k8 servers (not specifically wds that i can remember), only a full server reboot seems to fix it. Matt

I've just created a .reg file and .bat file for you. Dump them both in netlogon, and point the logon script at the AddressBar.bat file. Matt AddressBar.zip

I assume then that you have home directories in the same format as username. That script is far simpler then than mine. To change the folders as well do: for /d %%i in (*) do subinacl /errorlog=subinacl.err /file %%i /setowner=%%i As well as the previous script. Matt

I have a script that will change ownership on home directories using subinacl. It enumerates an OU for all users, reading their homedirectory path and username, and passes these to subinacl. Let me know if you want it. Matt

It's a User setting, so logon. Matt