Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Eman

  1. Hello, I have an HP database server hooked up to an MSA 1000 SAN disk subsystem (detached fiber storage), and was running performance monitor (perfmon) on the server itself to log various system counters that I look at during performance and capacity testing. Last week, I was messing around with the disk arrays on the SAN (with disks that were NOT being used by the system!), and created a new array, made it a dynamic disk, etc. It did not contain any of the database information or anything else, it was simply being used as a playground. Around that time, it seems that my perfmon physical disk counters failed to log anymore, with an error of "unable to add the counter" in the application event log. Using the "Add" button in the perfmon GUI, I can't even see Physical Disk on the list of coutners to add! The CSV log files don't even have a column for them now. I've tried using "diskperf -y" and its associated commands, even "diskperf -n", reboot, "diskperf -y", reboot, and no luck. I've since removed the dynamic disk and new array I created on the SAN, and re-tried the diskperf commands and adding them in perfmon again, but still can't see the physical disk counter. Anyone have any idea what's going on? Thanks. (I should add that the server in question is running Windows 2000, with the latest SPs and patches).
  2. Wow, thanks for the code - I might give that a shot on my 2000 machine. I assume you run this on the client? (Or run on the WUS server?) Not encouraging to hear WUS as buggy though. I'm mystified why my 2003 client did not show up either. I guess I can understand 2000, since it's older, but since WUS was kinda built for 2003, it seems that it would support that client easily. Question: is BITS required on the client machines as well? I only installed it on the server.
  3. Hello, I've recently installed the latest beta for Windows Update Services (along with BITS 2.0) onto a Windows 2003 machine. I then went to 3 different client machines to configure them to point to the new WUS server according to Step 5 in the WUS "Step by Step Guide to Getting Started". One of the clients has XP sp2, one has 2003, and one has 2000 sp4 on it. After I made the gpedit.msc changes, the XP machine showed up in the WUS Admin interface (the web-based one) under "Computers". So that was good. However, the 2003 and 2000 machines did not, and I can't figure out why. I've rebooted them, double-checked the gpedit settings, etc. But to no avail. All 3 clients sit in the same room, under the same network configuration - so all 3 have access to the WUS server. All 3 clients use the same logins, all with Admin priveliges on them. Does anyone have any suggestions? I realize this is a new product (beta still), but hopefully I can find someone here to help. Thanks!