Try:

1. rsm view /tlibrary then use result for rsm /refresh /lf"library_name" (eg rsm refresh /lf"IBM ULTRIUM HH-3 TAPE DRIVE")

2. restart rsm service

3. compmgmt.msc; removable storage; work queue; errors, delete jobs, etc

4. rebuild rsm database:

1) Go to Start > Control Panel > Administrative Tools > Services and find the Removable Storage service.
2) Right click on the Removable Storage service, select Properties, change the ‘Startup type:’ to Disabled and click ok.
3) Restart the machine
4) When the machine is running again open Windows Explorer and navigate to the C:\Windows\system32\ntmsdata\ directory  (or some other variation depending on the operating system, just pick the directory where Windows is installed and go from there)
5) In that directory rename all the files to *.OLD or move them to another temp folder.
6) Go back to the Removable Storage service (see step 1) go to properties and change the ‘Startup type:’ back to Automatic.
7) Restart the machine again

Error message appears upon extending disk volume in Disk Management and new size isn't reported in Explorer (although is in Disk Management).

Solution

DISKPART

DISKPART> List volume

DISKPART> Select volume #

DISKPART> extend filesystem

DISKPART> exit

(Works on 2003 post SP1, Paragon allows for system partition expansion (in realtime)))

%systemroot%\Inetpub\Adminscripts

adsutil.vbs Set MSFTPSVC/DefaultLogonDomain "DOMAIN" [include quotes]

Restart FTP service

 

One or more of the following:

1. In adapter's TCP/IP DNS properties untick "register in DNS"
2. Stop DNS server listening on IP of adapter
3. Add the following DWORD = 1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Interface name>\DisableDynamicUpdate

 

Disable the following Windows Server 2003 services:

1. ERSvd - Error Reporting Service
2. HidServ - Human Interface Device Access (keyboard buttons, remotes, etc)
3. IsmServ - Intersite Messaging (except for AD replication across subnets, smtp intersite replication, etc)
4. ScardSvr - Smart Card Access
5. LMHosts - TCP/IP NetBIOS Helper (no legacy hosts)

 

 

Sharepoint Central Administration
Virtual Server Configuration
Configure virtual server settings
Default Web Site
Virtual Server Management
Define managed paths
Add New path -> certsrv -> Excluded path
OK

See: http://www.microsoft.com/technet/prodtechnol/biztalk/2006/library/a4swift/39916663-b80e-49d8-ba9b-49276eb564fc.mspx?mfr=true

Can't install Service Pack (or some/all other updates) directly, from Windows Update or by WSUS.  See http://support.microsoft.com/default.aspx?scid=kb;en-us;822798 for solutions.

This worked for me:

create batch file (catroot2.cmd)

net stop cryptsvc
ren %systemroot%\System32\Catroot2 oldcatroot2
net start cryptsvc
cd %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
del /Q tmp*.cat
exit

Then delete all tmp*.cat files from %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} (or add to batch file, as above)

Just some notes:

http://support.microsoft.com/kb/926182

---

I order to run  an IPSEC/NAT-T type VPN you need to insert the following registry keys on the client :

XP SP2:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPsec]

 "AssumeUDPEncapsulationContextOnSendRule"=dword:00000002”

Vista:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent]
"AssumeUDPEncapsulationContextOnSendRule"=dword:00000002”

Now... I'm not quite sure that these alone will help you get connected.
Make sure that since you are connecting from a non-domain member that you certificate is properly installed.

Import the Administrator-Cert to both
Local Machine: "Personal" & "Trusted Root Certification Authorities"

This in combination with the above registry-hack should do it.

BTW: The one for SP 2 is documented in: http://support.microsoft.com/default.aspx?kbid=885407

The one for Vista is not... but it works  

[TX Geir Johansen, isaserver.org]

---

OK, here is a way to do it (but it is not an easy
solution).

1) You need to use certmgr.msc on the Vista Client
2) You need to generate Custom Request in the console
(see Create a Custom Certificate Request in the Help
file).
3) Best to add Custom subject information (be sure to
include an Alternate Name that includes the User
Principal Name
4) Save the file to a PKCS#10 request

Create a custom v2 certificate template that allows the
Subject to be created in the Request. Base it on the
template you want to use (for the love of G*D, do not
use User <G>) Ensure that the template is available at
the CA you are using. Assume it is named VistaUser

You now use the Certsrv Web page to submit the request
1) Connect to https://CAName/certsrv
2) Provide credentials from the domain
3) Choose Request a Certificate
4) CHoose Advanced Certificate Request
5) Choose Submit a certificate request by using a base-  
64-encoded CMC or PKCS #10 file, or submit a renewal
request by using a base-64-encoded PKCS #7 file.
6) Paste the contents of the file created in the first
procedure into the Saved Request box
7) Choose the VistaUser template in the Certificate
Template sectino
8) Click Submit
9) Save the issued certificate to a PKCS#7 file (all
certs in the chain)

Go back to the Vista box
1) Import the PKCS#7 file
2) Put all certs in the Personal store (for now)
3) Once the import is complete, move the CA certificates
into the appropriate stores (root in the root, all other
CAs in the intermediate store
4) Use the certificate

Brian
P.S. Please do not ask for more detailed steps <G>

In article <D85CB163-D832-4D40-B009-B5A28A685BF0
@microsoft.com>, S...@discussions.microsoft.com says...