If you take a look at the Readme.txt file on IBM's ftp site (use the /Latest, 
not WHQL):

ftp://ftp.software.ibm.com/storage/devdrvr/Windows/Win2003/Latest/

4) Version 6.1.6.2 and later versions of the device driver have an option for 
enforcing file names for
   tape drives that will persist across reboots of the operating system.  For 
example, if your tape drive
   has the name \\.\tape3 and the persistent naming option is used, then 
\\.\tape3 will be reserved for
   use by that device after an operating system reboot.  To take advantage of 
this feature, place a DWORD
   value in the registry called PersistentNaming and assign it a value 1 at:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3

   and reboot your system.


This isn't "Persistent binding" because the issues in Windows aren't related to 
FC binding. Even if devices are correctly setup to persistent bind, they will 
still have reordering issues under Windows. The issue is the Window Plug & Play 
driver will dynamically assign storage devices names starting with \\.\Tape0, 
etc.. Once you modify this registry setting the devices will show up as 
\\.\Tape<SerialNumber> which will persist.

There is a similar fix on technet for non-ibm drivers. Again, it doesn't have 
anything to do with FC binding (the reason for confusion is that under unix 
persistent binding and persistent naming are the same, but not in windows)

For windows 2003:
http://support.microsoft.com/kb/873337

For Windows 2000:
http://support.microsoft.com/kb/889330/


----
Matthew Huff       | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com     | Phone: 914-460-4039
aim: matthewbhuff  | Fax:   914-460-4139

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Alexander Kaasjager
Sent: Friday, June 27, 2008 10:29 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Persistent Binding Issue (again)

> ...
> >We had an incident yesterday following the reboot of our Networker 
> >Server with the monthly MS patches where we could not 
> control the tape 
> >drives and Networker was confused as to which tape drive was 
> which (the 
> >persistent binding thorn in our sides).
> ...
> 

>> Did you try Microsoft's hotfix for this problem? 
>> KB #873337 (http://support.microsoft.com/kb/873337/) is 

> Yes - we've tried that in the past and it apparently does not work...


Including the registry setting? It is somewhat below in the article,
I've
seen people read over it - unfortunately, that setting is exactly what
should solve it.
And is the Removable Storage service disabled?

Best of luck,

Alex

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER