Search results for query: *

Can people list some obvious reasons why not to use Roaming profiles? My boss is thinking about implementing Roaming profiles but I think it's a bad idea because of network congestion in the morning when people log on for the first time and also the possibility of the profile becoming corrupted...

It never mentioned that all 32-bit apps aren't written for multithreading... I have an article here that says 32-bit apps are multi-threaded: http://kb.iu.edu/data/ahop.html

Can you point me to an article to back that up?

Do all 32-bit apps take advantage of multiproccesors?

Is there a clear way to spot if an application is 16 bit or 32 bit? I found an article from MS (http://www.microsoft.com/windowsxp/using/security/learnmore/spot16bit.mspx) about spotting a 16 bit application. I right-clicked on an app of mine in question and it did not have a version tab...

I am having difficulty troubleshooting our Windows 2000 Server where the "system" process is hogging a lot of CPU usage, causing the total CPU usage to be at or above 90% most of the time. I ran pstat on the server and will post the output here, to see if anyone can see something suspicious...

Any tools I could use to see what percentage of the SYSTEM process something is using?

As of yesterday on our Windows 2000 server our CPU usage has been up in the 90s and sometimes pegged at 100%. Every now and then it will go down to the 70s and 80s but briefly. In task manager it shows the SYSTEM process with a PID 8 that is hogging the majority of the CPU. We have Norton...

So I would need to do scenario 2 before I perform adprep and forestprep?

Has anyone done this before?

I'll need to keep it in mixed mode. I read an article about extra steps needed when there's an Exchange 2000 Server involved because it alters the schema. There's some stuff that needs to be done first.

What additional steps are involved or precautions to take when promoting a 2003 Server to a Windows 2000 domain with an Exchange 2000 server? Thanks.

Is there a workaround if your RIS image has a larger hard drive than your target machine? I get the error: Setup cannot copy the operating system you selected. This computer does not have enough disk space on the selected partition.

See where you say one thing and then the next? I think you meant that I'm suppose to use the Adaptec utility to create the mirror, I read in the manual that you use it for migrations. It doesn't say how but I'm sure I'll figure it out after I install it. Is this what you meant?

I just saw that the Adaptec Storage Manage Utility will let you perform migrations. Is this what you were talking about?

You're confusing me! You say Seagate and then you say Adaptec to mirror. I don't see either option anywhere, and I have read the documentation that came with the controller. It also says I need to initialize my drives to create an array. Right now it shows this when booting the controller...

In the Array Configuration Utility is lists the drive as a legacy array. Won't I still need to change this to a RAID 1? If I go to create an array in the ACU, it says there are no free initialized drive space available to create arrays, please initialize drive(s) to create free drive space for...

Our Windows 2003 server is running out of disk space on our data partition. Is there a way I can back up a few of my RIS images (that are rarely used) to tape or DVD, and then restore them if needed? If so, can someone tell me the proper procedure? Thanks!

I think what I'm taking away from your explanation, is that I need to connect both U320 drives to the RAID controller and set my array to RAID 1. Boot the server with the 2940 and U160 drive along with the RAID controller and two U320 drives attached. Then go into Windows Disk Management and...

Also, since I've had the 29320 scsi card with the tape drive attached to it (nothing else). Disk management has been acting wierd. It took forever to make any progress when regenerating my mirror, and now when I bring up disk management, it just says "connecting to logical disk management...