Zer0kbps

Hi People, I hope someone can help me out here, I have setup a new exchange 2007 server on a windows 2008 member server in a 2003 Active directory. The installation finished ok, all the services have started, I chose the typical install with outlook 2003 clients connecting, and generally left everything stock. I have created all my mailboxes setup a few computers with outlook sent emails and nothing arrives in the inbox. The information store is working because when I login as the same user on multiple computers I can see the sent items folder contains everything that's been attempted to send thus far. I don't see a SMTP service is that right? I don't get any NDR's unless the time-out is not set. Pretty much everything is default

We have been using them for a very long time, I personally hate them with a passion, but they do the job,it's just over the years they get smaller but the problems never disappear, like others have said, ribbons break so have sello-tape to hand. The bit the vexes me so much is the amount they waste on the ribbon, when u install a fresh ribbon it skips the first two sets of cells, and then it's the drivers, they are ok but they could be better. Tbh i think they are the best of a bad situation, a lot of the edu sector seem to use them, my advise is to get cards pre-printed with all static stuff and simply print off the dynamic bits, this cuts the print time downs. If you can live with it try black only printing, quailty could be better, but by god it's fast and cheap because of the way the colour works.

Well it appears a total reboot on the machine in question cured this one, there must be some sort of local profile caching going on, but after a reboot of computer1, the user started to write its profiledata to our shared profileroot$ on the server.

We are rigging up our roaming profiles for our budding students, an oddity that concerns me while setting it up was. we had 2 computers to test the same account with. we logged on to computer 1 before we had setup the shared profileroot share on the server, it logged in fine and created a local profile under the usual documents and setting\username. Anyway realising the error of our ways, we created the shared profileroot$ share, re-pointed the profile path in AD, logged out of computer1. we then re-logged in computer1, checked the profileroot$ share, and no profile folder, thinking it was a permission fault, checked that all users had read write access to the profileroot$ share, which was the case. logged out and logged in a few times on computer1, thinking it was a delay on the DC's yielded no desired result. logged on in computer2, surprise surprise, the users profile folder was created as it normally would be, when we logged off the hive data and the relevant folders where uploaded. meanwhile back on computer1, it was having none of it, until we nuked the local profile. My question, how can I ensure the profile on the server takes the lead when I potential clash occurs?

This is cool, geeks and bikers, anyway, living in Hinckley n all I ride the obvious brand for my town, I ride the big cat with the 1050 lump, the one that's not really designed for off-road duty I like fast looking bikes, not too much chrome.

does the fn + brightness adjuster not work? also can you not set the brightness in the bios? if it's really dark, maybe the backlight is failing, but that would be dark all the time including when you first crank it up.

if the kms service is running on a windows 2008 box it requires only a minimum of 5 activations to work. On another note, does anyone know what sort of dns srv records are created?

Well folks, today we have done 161 without any major problems, we did have a weird quirk involving the mini set-up not asking for the hostname to be set, but a power cycle of the unit solved this. Speed wise, in one room we had 20 going at 450MB/Min, and the other 34 at 609MB/Min our poor ghost server certainly felt the pain today but it's arddd! The image took 20mins to drop down and I am now happy, we even left them on legacy, I cannot help thinking it's one of problems involving a conflicting interrupt, these problems never really occur much except in dos I will say it again. to fix simply set Sata Operation in the bios to Legacy

fixed it, in said computers bios, set the sata operation to Legacy, not ACPI or ATA!

Cheers chaps, We have set the bios to ATA already, we also tried a few other things like speed step, and hard disk accoustics, didnt work mind.

We have like many, procured our summer allocation of computers (Dell Optiplex 760 Small Form), they turned up yesterday, we un-boxed them and set them up in our imaging lab. We had 20 on a session and that's when hell was realised! Image just one (forced multicasting for the test) and we get a solid 690MB/Min on ghost 8.2 Image two or more and we get 2-6MB/Min, now we tried this on both multicast & unicast! We tried a few different specs of computers two hpdc5100 on the same cables produced 600+MB/Min, Even the Steps taken so far. Downloaded the latest packet drivers from Intel for the nic in the machine, this yielded no difference at all. Tried them on their own switch with fresh cables, no wimpy switch either, Cisco 2960G, still no joy. Our last solution is not ideal, but we will put the hard drives in to other computers and image. Dare i ask if anyone else has seen such problems before? It feels to me like a faulty network card driver/firmware

i remove the default gateway, and add routes for the pain in the a£"$ apps that wont proxy via dhcp static routes. keeps the load of the firewall amongst other things, and stops p2p pretty good