kurbycar32

your right about the unattend.xml file not helping on start up. the settings for many of those features are queued to happen on start up as part of the sysprep process, meaning it executes those commands before shutdown and before you extract your image. your problem seems simple though. instead of using the sysprep process to create your accounts write a script to create them on first startup, that would be easy enough to edit and you could guarantee that it ran after the first boot. also depending on your environment you could manage accounts using group policy

It turns out my mistake was that I was trying to think for myself. The solution was to create the local admin account as part of sysprep. I thought this was redundant because the account already existed but I guess that’s just how it works. it appears that you must create a local account but you can make that account the local administrator, which you would have anyway

im saying you wont notice the difference between having the 4 or 6gb so use only the faster ram for a total of 4gb at DDR6400. your actual usage even with encoding videos will be less than 2gb. hook it all up and check your memory usage. if im wrong send me a screen shot of the performance tab of your task manager. my vista machine idles at 658mb ram usage. no real tweaks, i just shut down the sidebar and turned off a few annoying "features"

I have vista Business 32bit using the WAIK to create the unattended.xml file. i have everything figured out except on initial boot it asks me to create a new local user. i dont want any local users except the local admin account, everything else is handled by the domain. I searched the MSFN before posting and didnt find anything.

im assuming your talking about mixing and matching using dual channel mode. as long as the banks match each other you should be fine. all memory will run at the slowest speed and windows XP32 bit will probably only recognize 3.25gb but i think you already knew that. i doubt you will see any performance difference unless your actually using more than 2gb of ram. my vista install consumes about 1gb of memory on idle, leaving 1gb for programs to hog up. gaming doesnt usually consume it and neither does encoding/decoding videos. if your like me though and you want the memory anyway (i have 8gb and use less than 2) i would pull out the 2 slower chips and just run the 4gb of faster memory, then sell your old stuff. since your not going to see a performance gain in capacity you might as well get the speed increase from the faster DDR.

you cant ping via hostnames at all neither domain or computer, even after a dnsflush. only TCP/IP and AEGIS v3.101 (802.1x) protocols are running. i havent tried disabling a lmhosts lookup, il give that a spin

prior to joining the domain the laptops are pointing to its DNS assigned by DHCP, the AD DNS server. the dns server is in perfect working order and considering the fact that the problem occurs regardless of the network it ends up on, even after disjoined from the domain. i would say that it doesnt matter. it is my beleif that in the process of joining the domain some part of windows is getting corrupted but i dont know what it is or what specificly is causing it. but to answer your question the AD DNS server can ping anything i tell it to. The problem lies within the laptop, but is caused by somthing that happens while joining the domain. thats my best guess

the firewall is disabled and manually setting ip and dns information doesnt work. it also doesnt matter what network you are on, like if i take it home and use it on my personal network it still fails. you can still browse web pages if you know the IP address though. our district has 26 schools up and another 4 being built and they are all on a 100mb WAN. everything is on server 2k3 as well but its poorly managed and understaffed (4 techs for 26 schools) so most of our stuff has to be done on location. i am trying to change that but im just one guy and i just transfered here 2 months ago.

I work at a school district and we just got a pile of new Dell D610 notebooks with intel pro 2200gb wireless network cards built in. the laptops come pre-loaded with SP2. Everything works fine until they are joined to the domain. when they join the domain all of the laptops loose DNS capability when using the wireless card to connect to any network. To troubleshoot i tried dis-joining the domain and logging on locally, doing a repair install and even using a different wireless card. nothing worked. the only way i got it working was formatting and loading XP with SP1. does anyone have any ideas?

ok so heres a quick description of what i did. made mac run linux, made linux run rdesktop on startup, removed linux GUI. now the mac is just a thin client: exactly what i wanted. heres the problem: the thin client auto connects but does not auto-log in, and i dont want it to. so it sits at the login screen for exactly 2 minutes and then disconnects and drops you back to linux command line (scaring the crap out of the user) question: how do i make the server leave the RDP session open indefinatly even if the client doesnt log in?

the nics are set on 100 base full duplex. also remember the raid is only for storage, my OS is running on a single drive. if i loose the OS disk i can reinstall and import a foreign volume so disaster recovery wouldnt be too bad. i am goign to run this as long as it runs, then if it ever dies il replace the board with a mini ITX with gigabit network and a PCI slot for a real raid controller, or hell it might have on board raid. on a side note, if i tell the bios to not halt on any errors can i boot this with out a video card? i remote into it anyway. if its possible i could put a raid card in there

smokee i looked into what you were saying and it checks out. so even though i am not seeing the performance my drives are capable of, i am very close the the 100mbit bottle neck anyway. since this will only be accessed across the network my speeds are acceptable. is that what your saying?

found the source of the problem. i benchmarked the drives using my quicktech bootable diagnostic disk and each drive is only pushing 10mb/sec. that explains why i am getting 23-27mb in a raid. the diagnostic utility is OS independant and i tested the drives individually so raid overhead and cluster size were not factors. its running a 440bx chipset with a ATA 33 IDE controllers, that are supposed to support up to 33mb/sec and my drives are all capable of higher speeds. my dma settings are all in the on position any other ideas?

i changed the block size to 16k and ran sis sandra again. as expected i took a hit on write speed (14mb/sec still way to low) and my read speed increased to 27mb/sec. when going over the results i found that sandra uses a 1024 block size for benchmarking and i dont think i can adjust it. i think my raid setup is super sensitive to block sizes because my celleron doesnt have any cache. on another system (running an athlon 64 1mb cache) the block sizes made almost no difference. i am going to try one of the benchmarks that was used in the raid article you referred me to and see if i can get some different results

that was a great guide. i never knew the speed differences with the cluster sizes so when i was setting it up i just figured "bigger is better". the benchmarks on that guide show that on average that is just the opposite and that clusters of 4-16k were best overall. since i dont have any data on the drive i am going to format them and configure the raid for a 16k cluster. il report the results