Questions[windows-server-2003-r2](server)

Under Linux, we can monitor SSD wear fairly easily with smartmontools whether the drive is presented as a normal block device or a generic device (which happens when the drive has been hardware RAIDed by certain controllers such as the one on the IBM HS22).

How can we do the equivalent under Windows? Does anyone actually use smartmontools? Or are there other packages out there?

The problem is that SCSI Generic devices just don't show up in Windows. If the drives aren't RAIDed we can see them fine.

How I'd do it in Linux:

sles11-live:~ # lsscsi -g
[1:0:0:0]    disk    SMART    USB-IBM          8989  /dev/sda   /dev/sg0
[2:0:0:0]    disk    ATA      MTFDDAK256MAR-1K MA44  -          /dev/sg1
[2:0:1:0]    disk    ATA      MTFDDAK256MAR-1K MA44  -          /dev/sg2
[2:1:8:0]    disk    LSILOGIC Logical Volume   3000  /dev/sdb   /dev/sg3

sles11-live:~ # smartctl -l ssd /dev/sg1
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.32.49-0.3-default] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Device Statistics (GP Log 0x04)
Page Offset Size         Value  Description
  7  =====  =                =  == Solid State Device Statistics (rev 1) ==
  7  0x008  1               26~ Percentage Used Endurance Indicator
                              |_ ~ normalized value

sles11-live:~ # smartctl -l ssd /dev/sg2
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.32.49-0.3-default] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Device Statistics (GP Log 0x04)
Page Offset Size         Value  Description
  7  =====  =                =  == Solid State Device Statistics (rev 1) ==
  7  0x008  1                3~ Percentage Used Endurance Indicator
                              |_ ~ normalized value

For the life of me I cannot figure out how to remove an iSCSI target (Dell Equallogic SAN) from a Windows Server 2003 box. The volume shows up in Windows as drive letter Y.

Using the iSCSI initiator, I can remove the Target Portal, but cannot remove the Target itself.

Can someone give me some guidance on this?

I've gone as far as setting the volume offline in the Dell SAN management tool, and even permanently deleted the volume. The Target no longer shows up in the iSCSI Initiator properties, but the drive letter is still there under My Computer. And now Windows is throwing delayed write errors for that drive.

There must be a proper way to successfully remove an attached Target.

I just installed Windows Server 2003 (64bit)

Because the Administrator password was blank I went to cmd > "net user Administrator newpass"

The command completed successfully.

Logged out, Logged back in. Also rebooted.

I go to control panel > system > remote > enabled remote desktop on this computer

Apply.

Go to Select Remote Users, it says "Administrator already has access" however I cannot login as administrator. So I added it into the list anyway. OK, Apply, OK.

I can connect to the server via RDP and get the login screen (so NOT firewall problem). I enter Administrator with newpass but I cannot login.

I have ensured that both systems have the UK keyboard layout and that the password I am using is the same (I preview it in the username field before moving it to the password field and is the same as it was in cmd.

So RDP is enabled, I can connect, but I cannot login as Administrator for which RDP has been enabled. Rebooted again. Hoping to find a solution to this awfully strange problem.

Thanks Chris

Edit: OK this is really strange, this time I changed the password via Computer Management not CMD and rebooted again. On startup I could not login to the server - im thinking oh crap, iv locked myself out. I RDP and the password works fine. I logout of RDP and try again on the actual server and again it doesn't work. eek. not sure what iv done wrong here ^_^

Edit: For some reason when I was logged in on the server, the keyboard was UK, the RDP login screen is UK, but the actual server login screen seems to have reverted to US.

Edit: The silent ALT+SHIFT trick switches the keyboard between US and UK, now just to ensure UK is the default, I guess by changing the registry ... if anyone has steps for setting the loginn screens default keyboard layout to >UK< that would be usefull.

First off, I have read through this post and a whole slew of non-SF posts which seem to address the same or a similar problem, however I was still unable to fix my problem.

I've got three machines in this situation:

• a domain-joined server that runs Server 2008 R2 Enterprise ("share server")
• a domain-unjoined test server running Server 2003 R2 SP2 ("test server")
• a domain-joined workstation running XP Pro SP3 ("workstation")

The share server is exposing a share on the network that the test server must access--it's a Source/Symbol Server share for our debugging purposes. I believe visual studio simply accesses the the share with its own credentials in this case, meaning that the share must be accessible anonymously since the test server isn't joined to the domain and there's no opportunity to supply domain authentication.

I've attempted a lot of things to avoid the authentication window when accessing the share:

• I've enabled the Guest account on the share server and given Guest full sharing/NTFS permissions for the share.
• I've given ANONYMOUS LOGON full sharing/NTFS permissions for the share.
• I've added my share to “Network Access: Shares that can be accessed anonymously” in LSP.
• I've disabled “Network access: Restrict anonymous access to Named Pipes and Shares” in LSP.
• I've enabled “Network access: Let Everyone permissions apply to anonymous users” in LSP.
• Added ANONYMOUS LOGON to “Access this computer from the network” in LSP.
• Added the Guest account to “Access this computer from the network” in LSP.
• Attempted to provision the share using the Share and Storage Management MMC snap-in.

Unfortunately when I attempt to access the share from the test server, I still see the prompt and I'm forced to enter "Guest" manually.

I also tried this workflow using the local administrator account on a workstation, and the same thing happens both with and without XP Simple File Sharing enabled.

Any idea why I'm getting these results, or what I should have done differently?

I've searched, but I can't find anything that explains why Microsoft started labelling new versions of Windows Server (and now SQL Server) as R2 releases.

If they're new releases, why not simply give them new names?

Or is there something going on with upgrade pricing or licensing?