nmX.Memnoch

What are the BSOD errors you're getting?

The only option you have for graphics on that screen is to set a Wallpaper. This is a simple registry edit of the following value: Key: HKEY_USERS\.DEFAULT\Control Panel\Desktop Value Name: Wallpaper Value Type: REG_SZ Value Data: Full path to the bitmap image you want to use. There are other options available for adding text to the Ctrl+Alt+Del dialog, but none for graphics.

I missed that. Here's the link to the Group Policy stuff:http://technet2.microsoft.com/WindowsServe...6deecd1033.mspx With the current setup, you're correct. However if they add any more servers later, planned or not, then they'll have to purchase more CALs. I've always recommended user Per User/Device for possible future needs.Although, if I recall correctly you can switch from Per Server to Per User/Device...just not the other way around. Personally, I never use Per Server...but then again I work in an environment where we have 10+ servers just for Exchange.

That's going to be impossible if the "other drive" is still FAT32. The problem isn't the application he's using to extract the file. The problem is that FAT32 has a file size limit of 4GB. No matter how you slice it you cannot have a file larger than 4GB on a FAT32 formatted drive/partition.

Almost any piece of software you install is going to require Local Administrator privileges on the workstation. Giving them Domain Admin privileges gives them access to screw up A LOT of things for EVERYONE...even if they don't do it on purpose. You should never give a user Admin privs on the local workstation. This limits them so that they can't install software (i.e. Spyware, Adware, Viruses) and helps to keep everything clean and running smooth. The thing you have to remember is it's not about making it easier for you to complete tasks, it's about making it harder for them to screw things up. Giving them Domain Admin gives them full access to every computer on the network...including the server. One rampant virus can take the entire thing down. As for the drive maps...drive maps are per profile. This is why you use logon scripts. You can have it automatically map the drives each time they logon. This can be something as simple as a CMD file or something as "complicated" as a KiX or VBS script. As for running Windows Update...this is something the systems administrator should be doing anyway. Create your own domain account and put that in the Domain Admins group. This will automatically give you local admin on all workstations and you'll be able to run Windows Update under your logon. However, instead of using Windows Update I recommend looking into WSUS (Windows Server Update Services). It's basically a local Windows Update server and you can approve or disapprove which patches to install. It can be setup to auto-approve certain types of patches...it's very granular so you can narrow it down to "all critical patches for Windows XP Service Pack 2" if you want. Once you get WSUS running you force the clients to use it through Group Policy settings for the Automatic Updates client. As for user profiles (Desktop, My Docs, Favorites, etc)...those are stored locally on the client by default. From the sound of things you want roaming profiles...which are stored server side. I've never done roaming profiles so hopefully someone else will step in and answer this one for you. Using roaming profiles will result in slower logons because everything has to be pulled from the server. If the network is decent they may not notice too much of a difference. The server upgrade will help to offset some of the speed. I also have a suggestion on your server setup. Instead of the 1800 go with a 2800. It'll offer you a little more upgrade room and doesn't cost that much more. I'd also look into changing the drive configuration to two 36GB 15K RPM drives in RAID1 for the OS and two 73GB 15K RPM drives in RAID1 for the data. You may even want to just go ahead and get four 73GB 15K RPM drives in RAID5 (so two 36GB/RAID1 and four 73GB/RAID5). The 2800 chassis has space for 10 drives so you can still add more later (the 1800 chassis only has 6 drive slots). Split up as much of the I/O as you possibly can by also getting the split backplane option as well. This way the OS and Data drive arrays will be on different channels of the RAID controller. As an aside, using KiXtart for logon scripts is something of a specialty for me. I'd be more than happy to help you get a basic one going so that you can see how to get started with things.

What exactly are you trying to edit?

I've had that happen before. More than likely it will work. Even if it doesn't at least you can get your system installed and then troubleshoot the problem afterwards.

MSI is definitely doing something other than limiting the amount of memory usage. This was taken from the ATI driver INF (from ati.com): "MSI RADEON XPRESS 200 Series" = ati2mtag_RS480, PCI\VEN_1002&DEV_5954&SUBSYS_71411462 Several other companies are doing the same thing: "ECS RADEON XPRESS 200 Series" = ati2mtag_RS480, PCI\VEN_1002&DEV_5954&SUBSYS_1B341019 "Sapphire RADEON XPRESS 200 Series" = ati2mtag_RS480, PCI\VEN_1002&DEV_5954&SUBSYS_0A56174B "ATI RADEON XPRESS 200 Series " = ati2mtag_RS480, PCI\VEN_1002&DEV_5954 If you notice, the device IDs are the same for all of them (PCI\VEN_1002&DEV_5954). The part that differentiates the motherboard manufacturer is the SUBSYS part. It really doesn't mean anything other than the motherboard manufacturer gets their name listed instead of ATI's. My point still stands in that the motherboard chipset is called the RADEON XPRESS 200, but the integrated graphics part of that chipset is based on the RADEON X300 GPU. The RADEON XPRESS 200 is comprised of many more parts than just the integrated graphics. Back to my original point, nearly any PCI Express add-in card is going to give you better performance than your current integrated graphics. I understand your reasons for not wanting to put an add-in card in the system right now. But to be honest, allocating more system memory to the integrated graphics really isn't going to give you any performance boost. Besides, the way graphics cards work is that they go out to system memory anyway if they run out of onboard memory (which in your case is the 128MB of shared system memory). In other words, if the graphics chip needs more than 128MB it's going to look to system memory for that anyway.

We did...I'm just glad to see someone finally explain that the half-open connections limit isn't a bad thing.

Double post... http://www.msfn.org/board/index.php?showtopic=70794 If you're using Windows 2000 or Windows XP you can convert the drive with the following command: convert X: /FS:NTFS Replaced X: with the drive to be converted. If this is your C: drive, I would recommend just backing everything up and reinstall choosing NTFS as the drive format during installation. The reason is because Windows 2000/XP apply different security settings to drives formatted with NTFS than they do drives formatted with FAT32. If this is any other drive then you can convert it withing any worries (you should still create a backup before converting the drive). There's no way to bypass it. This is a limitation of the FAT32 filesystem.

You definitely want to opt for setting up a domain vs. letting them use local user accounts. There are several reasons for this: 1. Probably the biggest...Group Policies. You can control all sorts of settings on the clients through Group Policies. 2. Centralized user management. 3. User accountability. With their current setup they have no way of truely knowing who did what. If something in the database gets messed up...how do you know who did it? Just because it comes from a particular workstation doesn't really prove anything...they all use the same username/password. 4. Security. This comes in with Group Policies and several other technologies inherit to using a domain structure. 5. Logon scripts. You can map drives, display messages, etc, etc using logon scripts. You really don't realize how handy they are until you start using them. Also, they should not all be setup with Domain Admin privs. This is extremely dangerous to the well being of your domain and network. To be honest, they really shouldn't have Local Admin access to the workstations either. One thing to note is that you will NOT be able to join the Windows XP Home machines to the domain. Windows XP Home was not designed for corporate networks and doesn't have the capability of joining a domain. Those machines will need to be upgraded to Windows XP Professional. Here's a TechNet article on Active Directory features and technologies: http://technet2.microsoft.com/WindowsServe...6241f91033.mspx And here's one on Group Policy: http://technet2.microsoft.com/WindowsServe...6241f91033.mspx

If you're using Windows 2000 or Windows XP you can convert the drive with the following command: convert X: /FS:NTFS Replaced X: with the drive to be converted. If this is your C: drive, I would recommend just backing everything up and reinstall choosing NTFS as the drive format during installation. The reason is because Windows 2000/XP apply different security settings to drives formatted with NTFS than they do drives formatted with FAT32. If this is any other drive then you can convert it withing any worries (you should still create a backup before converting the drive). There's no way to bypass it. This is a limitation of the FAT32 filesystem.

The number of drives supported is directly related to the number of SATA channels you have. So if you have two on your motherboard and then put in an add-in card with another four SATA channels then the total number your system can support is 6. Does the system POST but hangs trying to start Windows Setup? Also, who is the manufacturer of the Multi-IO card. I never really cared for cards like that because the usually mean cheap parts...and by "cheap" I mean substandard.

The difference in the shared amount of RAM has to be one of the differences between the M2 and M4 revisions of that board then. A BIOS update may give you the option to share more. Again, the overall chipset is called the Radeon Xpress 200. The graphics part of the Radeon Xpress 200 chipset is most definitely based on the X300 series GPU per the information quoted above directly from ATI. If you use the actual ATI drivers the display adapter will show as a "ATI RADEON X300 Series" display adapter. We have about 40 or so HP machines at work with the same chipset in them. I really wish that ATI would've come up with a different name for their motherboard chipsets than using the same Radeon moniker they use for their graphics chips. The average user gets confused by this.

Check Device Manager...it's an X300. The chipset is called the Radeon Xpress 200, but the graphics portion is a Radeon X300. http://www.ati.com/products/radeonxpress200intel/index.html http://www.ati.com/products/radeonxpress200/index.html Anyway, the only way you're going to get more video RAM is to get an add-in card. The capabilities of the integrated X300 you have now won't get any benefit from having 256MB of system RAM allocated to it. You'll lose performance from the overall system anyway because the rest of the system would only have 768MB available for use. An add-in card would give you back your full 1GB of system RAM instead of the current 896MB left over after allocating 128MB to the integrated graphics.

Have they tried opening it with Notepad or Wordpad? Have them save the file and change the extention to .txt. The .dat file may actually contain some information about what's going on...--------------------------------------------- EDIT: Google is your friend. http://support.microsoft.com/default.aspx?...kb;en-us;278061 SYMPTOMS When you use Microsoft Outlook to send messages through the Internet with attachments and you use the Microsoft Outlook Rich Text format, some recipients report that the message includes an additional file called the Winmail.dat file. The Winmail.dat file is usually very small, but you cannot open it in the message. The original message attachment is not always separate from the Winmail.dat file attachment, and may be included in the Winmail.dat file attachment. CAUSE This problem occurs because the Winmail.dat file is used to preserve formatting that the sending client includes in the message, but the receiving client does not recognize the Winmail.dat file. In Outlook, the Winmail.dat file includes Rich Text Formatting (RTF) instructions. This type of formatting is used with the Microsoft Outlook Rich Text format and when you use Microsoft Word as your e-mail editor. Click the link for RESOLUTION steps.

This should've gone in the Microsoft Office 2000/2002/2003/XP > Microsoft Outlook forum...but... I don't think the problem is with your mail client. This is more than likely happening somewhere between you and the recipient. Have you contacted your ISP yet to see if they have any suggestions? Also, what are the contents of the .dat file when the person recieves it on the other end? Is it the same file with a simple extension change? Or does the file possibly contain some information as to what may have happened to the original attachment?

The second line should be: net localgroup "Power Users" "username" /add Other than that, those are the two commands you need to run.

Just a slight suggestion though...I would use the .cmd extension instead of .bat. CMD files are the native format for NT based OSes. While BAT and CMD files are very similar there are some differences between the two.

I'm glad someone else realizes this... Half-open connections are a bad thing. Too many half-open connections can hurt your network performance. It's how DDOS attacks are generally carried out. Has anyone noticed that there have been a lot less large scale DDOS attacks since this limitation was put into XP SP2 and 2003 SP1?

Create your .REG files and load them (regedit /s refile.reg) during the GUI part of setup using CMDLINES.TXT. It works in the same way the Windows XP method does. Since at that point there aren't any users on the system, any HKCU entries will be added to the Default User profile, and therefore applied to all new users who logon to the system.

That would require changes at the hardware level...something that the average Joe won't be able to do. My suggestion would be to pickup an add-in video card so that you're not sharing system RAM at all. Your system will perform much better. Even a 6600GT or X600 based card would be better than the integrated X300 you have now.

Because prod.tele.com is the name of your domain controller. When doing LDAP queries you want to use the name of the Active Directory Domain...which in your case is tele.com. What you observed is the expected behavior.

I went ahead with the KiX script. You can grab the KiXtart executables from http://www.kixtart.org/ (646KB download). If you're running any NT based OS all you need from the zip archive is KIX32.EXE. Just drop it in %SYSTEMROOT% (your Windows directory). The manual is also included in the zip archive in case you want to browse through it. Now create a new empty directory. In that directory, create two new text files; one named remote_shutdown.cmd and one named remote_shutdown.kix. The KiX code below is documented so it should be fairly easy to decipher. If you want a good KiX editor check out AdminScriptEditor. It also does VBS, HTML, XML, CMD, AutoIt and several other languages. Copy and paste the following into remote_shutdown.cmd. %SYSTEMROOT%\KIX32.EXE .\remote_shutdown.kix Copy and paste the following into remote_shutdown.kix. /* -------------------------------------------------------------------- Author : Curtis Brabham Date : 22 Mar 2006 Purpose: Remote shutdown of multiple workstations. Note 1 : This script depends on a standardized workstation/server naming convention for successful operation. Note 2 : shutdown.exe requires that you have Administrator privileges on the remote computer. Instructions: ============= - Change the $TIMEOUT value to adjust the wait period before shutdown is initiated on the workstation. - Change the $COMMENT value to change the message displayed on the workstation/server prior to shutdown initiation. - Edit the $WKSTR value for the workstation string. Change ******** to a value that is common in all workstation names. Example: Computers in the Human Resources department of company XYZ use a standardized computer naming convention. The convention is: Company Workstation/Laptop Department Unique Number XYZ WK or LP HR ### So a workstation in Human Resources of company XYZ with an inventory ID of A31 would be named XYZWKHRA31. The common string for workstations in HR is "XYZWKHR" so you would set $WKSTR to "XYZWKHR". This would result in shutting down all workstations that are online in the HR department. -------------------------------------------------------------------- */ Break On $X = SetTitle("Running Remote Shutdown Script...") $TIMEOUT = "30" $COMMENT = "After hours automated shutdown script." ; ------------------------------------------------------------------ $WKSTR = "********" ; <<<<<<< EDIT THIS VALUE ; ------------------------------------------------------------------ ; Query for online workstations and dump output to a text file Shell '%COMSPEC% /C NET VIEW | FIND "$WKSTR" > "@SCRIPTDIR\workstations.txt"' ; Open the text file and read each line for workstation names If Open(1,"@SCRIPTDIR\workstations.txt",2) = 0 $WK = ReadLine(1) While @ERROR = 0 If InStr($WK,"\\") ; Trim trailing spaces from the text line $WK = Trim(SubStr($WK,1,30)) ? "Attempting to shutdown $WK" ; Run shutdown.exe for each workstation Shell '%COMSPEC% /C shutdown.exe -s -m $WK -t $TIMEOUT -c "$COMMENT" -f' EndIf ; Read the next line and loop back to the If statement $WK = ReadLine(1) Loop ; Close the text file after reading the last line $X = Close(1) EndIf ; Delete the text file. ; Comment this line out if you want to review the text file. Del "@SCRIPTDIR\workstations.txt" ; Exit the script Exit

It's limited by the speed of the onboard SATA controller speed. The PCI bus is only used to power the DIMMs and recharge the battery. The data is still transfered over one of the systems onboard SATA channels.http://www.giga-byte.com/Products/Storage/...Name=GC-RAMDISK