Free Joomla Template by HostMonster Reviews

Unable to create new backup folder. Access denied (Solution) Symantec Backup Exec 10d for Windows Servers

Only verified on Symantec Backup Exec 10d for Windows Servers

1. Create local account on NAS
2. Create local account on server(this cannot be a DC) that matches the NAS account. 
3. Make local server account a local administrator.
4. Set BE services to run under this account under Network Options and Services Options.

5. Within the Device Manager of the Windows System the Backup Exec Server is on, edit all 5 Backup Exec Services to login with the local account on the server that matches the NAS.

6. Restart all services within Device Manager or reboot Server.

7. Attach BE back to disk folder to UNC path which if above steps were followed it will connect.


Attempt to readd Backup to Disk folder.

Spiceworks Client Setup

Credit for this article goes to the Spiceworks Forum post it was found in.


1.       Admin ID TARGET: All Operating Systems

1. Set up an administrator ID that will be used on all computers in the network. This will have local (or domain) administrator and WMI rights.

2. Ensure that the ID and PW are entered into SpiceWorks

2.       Allow Ping TARGET: XP, Vista, 7 and Server 2008

Ping the target computer from a remote PC. If the ping fails (ERROR: Request timed out), follow these steps.

Allow firewall ports: 3,7,8,9,11,135,137,445 TCP + UDP

Netsh firewall set service remoteadmin enable subnet

Windows XP

1. Click Start

2. Click Control Panel

3. Double-click Windows Firewall

4. Click the Advanced tab

5. Click the Settings… button under ICMP

6. Check the Allow incoming echo request checkbox

7. Click OK three times

Windows 7

1. From the Start menu, search for Windows Firewall with Advanced Security.

2. Click it to bring up the application.

3. From the left pane, click Inbound Rules.

4. In the right pane, find the rules titled File and Printer Sharing (Echo Request - ICMPv4-In).

5. Right-click each rule and choose Enable Rule.

Windows Server 2008

1. Click Start

2. Click Control Panel

3. Double-click Administrative Tools

4. Double-click Windows Firewall with Advanced Security

5. From the left pane, click Inbound Rules.

6. Find the rule File and Printer Sharing (Echo Request – ICMPv4-In)

7. Right-click the rule and choose Enable Rule.

8. Close the window

3.       Enable Group Policy TARGET: All Operating Systems

You need to set a policy on the computer to allow access

Windows XP, Server 2003, Vista, 7

1. Click start

2. Click run

3. Type mmc

4. I clicked on "File" then "Add/Remove Snap-in".

5. I clicked on the "Add" button.

6. I selected "Group Policy Editor" and clicked on "Add".

7. Click Finish

8. Click Close

9. Click Close

10. Navigate to here:

Console Root

|- Local Computer Policy

|- |- Computer Configuration

|- |- |- Administrative Templates

|- |- |- |- Network

|- |- |- |- |- Network Connections

|- |- |- |- |- |- Windows Firewall

|- |- |- |- |- |- |- Standard Profile *

11. Double click on "Windows Firewall: Allow remote administration exception"

12. Set the configuration to "Enabled"

13. Type localsubnet in the "Allow unsolicited incoming messages from" field

14. Click OK

15. Click Start

16. Click Run

17. Type cmd and press Enter

18. Type gpupdate and press enter

19. You should see the following:

C:\Documents and Settings\Administrator>gpupdate

Refreshing Policy...

User Policy Refresh has completed.

Computer Policy Refresh has completed.

* Under Windows Firewall there is also Domain Profile. It is possible you can use either or both. I used Standard Profile and it worked.

Windows Server 2008

1. Follow steps 1 through 10

2. Step 11, double-click on Windows Firewall: Allow inbound remote administration exception

3. All steps after are the same

4.       Link Admin ID to WMI Control TARGET: All Operating Systems

1. Click Start

2. Enter compmgmt.msc in the search field

3. The Computer Management screen appears

4. Expand Services & Applications

5. Click on WMI Control

6. Right-click and choose Properties

7. Select the Security tab

8. Highlight Root

9. Click the Security button

10. Add the ID mentioned in PART ONE

11. Grant the ID Allow permissions for EM, FW, PW, PrW, EA, RE, RS and ES

12. Click the OK button

13. Click the OK button

NOTE: I have been liberal with granting permissions to a local admin ID. You should modify the settings to suit your own network security needs.

5.       Link Admin ID to DCOM TARGET: All Operating Systems

1. Click Start

2. Enter dcomcnfg.exe in the search field

3. Expand Component Services

4. Expand Computers

5. Right-click on My Computer

6. Choose Properties

7. Click on the Default Properties tab

8. Check the Enable Distributed…computer checkbox

9. Check the Enable COM…computer checkbox

10. Verify the Default Authentication Level: is set to Connect

11. Verify the Default Impersonation Level: is set to Identify

12. Click the Apply button

13. Click on COM Security tab

14. Click the Edit Limits… button under Launch and Activation Permissions

15. Add the ID mentioned in PART ONE

14. Grant the ID Allow permissions for LL, RL, LA and RA

15. Click the OK button

16. Click the OK button

NOTE: I have received this popup: Windows Security Alert – Do you want to keep blocking this program? Microsoft Management Console. I click the Unblock button.

NOTE: For Windows 7 and Server 2008, I received this message after step 12. Click Yes.

You are about to modify machine wide DCOM settings, this will effect all the applications on the machine, some applications may not work correctly as a result. Update DCOM settings?

6.       Local Security Policy TARGET: XP only

1. Click Start

2. Enter secpol.msc in the search field

3. This will open up the Local Security Policy window.

4. Click Local Policies

5. Click Security Options

6. Scroll down to Network Access

7. Choose “Sharing and security model for local accounts"

8. This should be set to "Classic-local users authenticate as themselves"

9. Click OK

10. Exit Local Policy

7.       Disable UAC TARGET: Vista and 7 only

1. Click Start

2. Type UAC in the Search programs and files field

3. Click on the "Change User Account Control Settings" link

4. Move the slider to the Never notify position

5. Click OK

6. If prompted to restart, do not, we will restart later

8.       Restart the Computer TARGET: All operating systems

Restart the computer for all changes to take effect

9.  Autostart - Distributed File System, Remote Registry, TCP/IP Netbios Helper.

10. ADD ALL users to RDP access.

11.       Test the Connection

NOTE: Use this code until you are shown a serial number (or the word None)

1. Click Start

2. Enter cmd in the search field

3. Enter the following at the c:\> prompt

wmic /user:[username] /password:[password] /node:[IP address or hostname] systemenclosure get serialnumber

[username] is the admin ID we set on each computer

[password] is the admin ID password we set on each computer

[IP address or hostname] is the FQDN or the IP address of the target computer

e.g. wmic /user:administrator /password:secretpassword /node: systemenclosure get serialnumber

4. Press the Enter button

Result should be:


None (or the actual computer serial number – like Dell service tag)

Microsoft Security Essentials is not recognized by Microsoft Security Center

This is a compilation of changes made to Windows XP PCs to fix the Red \"X\" Shield that Microsoft Security Essentials shows when it is not loaded properly.

Click on the START menu

Click on RUN

Type: services.msc

Press OK

In the next box that comes up, scroll down to the services called \"Remote Procedure Call (RPC) Locator\"

Double click on it

Change the startup type from Manual to Automatic

Then click on the RECOVERY tab

Set all the failure recovery actions to \"Restart The Service\"

Click APPLY then OK

Security Center within services.msc was set to \"automatic (delayed start)\", I set it to automatic.



Winmgmt /resetrepository


  1. Note this will reset repository to the initial state when the OS was first installed
  2. Windows XP and Windows Server 2003, there are no built in switches to rebuild the Repository, so you must do it manually.


Warning: Rebuilding the WMI repository has resulted in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository. 


If /salvagerepository or /resetrepository does not resolve the issue, then manually rebuild repository:


  1. Change startup type to Window Management Instrumentation (WMI) Service to disabled
  2. Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
  3. Rename the repository folder:  C:\\WINDOWS\\system32\\wbem\\Repository to Repository.old
  4. Open a CMD Prompt with elevated privileges
  5. CD windows\\system32\\wbem
  6. for /f %%s in (\'dir /b /s *.dll\') do regsvr32 /s %%s
  7. Set the WMI Service type back to Automatic and start WMI Service
  8. cd /d c:\\  ((go to the root of the c drive, this is important))
  9. for /f %%s in (\'dir /s /b *.mof *.mfl\') do mofcomp %%s
  10. Reboot the server


Vista SP2 fails to install, error trust_e_nosignature (0x800b0100)

This just saved a customers laptop from a format.


This is how I fixed mine. I had the same issue. When I tried to install SP2 from Windows updates I was getting a TRUST_E_NOSIGNATURE error. I downloaded and ran the CheckSUR tool but I still was not able in install SP2 from Windows Updates. I downloaded the standalone version of SP2 and it would not install. Said that I needed to install SP1 first but that was already installed. I tried to uninstall SP1 but it was not listed in my Installed Updates list. I tried to uninstall it with the command line but that would help either.

This is what I did to fix my problem.

Note: You may need to use some common sense and apply the below for YOUR situation.

1. Download and run CheckSUR (System Update Readiness Tool)
2. Open %SYSTEMROOT%\\Logs\\CBS\\CheckSUR.log (mine is below)

Checking System Update Readiness.
Binary Version 6.0.6001.22375
Package Version 5.0
2009-09-08 20:40

Checking Deployment Packages

Checking Package Manifests and catalogs.

Checking package watchlist.

Checking component watchlist.

Checking packages.
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Microsoft-Windows-VistaServicePack-SysHiper-SP1-Package~31bf3856ad364e35~x86~~6.0.6002.18005.mum  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_10_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_11_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_14_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_15_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_5_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_6_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_7_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_8_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_9_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_for_KB948465_client_1~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_for_KB948465_client~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\Package_for_KB948465~31bf3856ad364e35~x86~~  
(f) CBS MUM Missing 0x00000002 servicing\\packages\\VistaSP2-KB948465~31bf3856ad364e35~x86~~  

Checking component store
Seconds executed: 1749
 Found 14 errors
  CBS MUM Missing Total Count: 14

3. Download the update that is blocking the install. In my case above, it was the SP2 updateKB948465
4. Extract the downloaded update to a temp folder using:

Windows6.0-KB948465-X86.exe /x:c:\\temp

5. Extract the CAB file (windows6.0-kb948465-X86.cab) to a new folder.
6. Navigate to %SYSTEMROOT%\\Servicing
7. Take ownership of the Packages folder and add your account to have full control
8. From your CheckSUR.log, find the files that were missing in the folder that you extracted the CAB file to in step 5 above.
9. Copy the .MUM and .CAT files to the %SYSTEMROOT%\\Servicing\\Packages folder
10. For the file that was missing, use the Update.MUM and Update.CAT files but rename them ie. I needed to rename my Update files to VistaSP2-KB948465~31bf3856ad364e35~x86~~ and VistaSP2-KB948465~31bf3856ad364e35~x86~~
11. IMPORTANT: Change the ownership of the %SYSTEMROOT%\\Servicing\\Packages folder back to \'NT Service\\TrustedInstaller\'
12. Re-run the SP2 stand-alone update.

Hope that helps out a few of you. 


Awesome. This fixed an issue I was having with a HP laptop that downright refused to install Vista SP1. I had first removed Net Framework and reinstalled as it would not update or install properly using the net framework removal tool  http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip?sa=676773226 then re-installing net framework and had re-registered all the dll\\\'s for windows update following instructions that I found somewhere on the net and apologies for not giving the correct attribution however as follows:

\\\"General Windows Update Troubleshooting

The following outlines how to stop services pertaining to Windows Update, rename system folders, register related DLL files, and then restart the previously mentioned services. This troubleshooting generally applies to all Windows Update related issues.

 Stopping services pertaining to Windows Update

  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
  2. If you receive a notification from User Account Control simply click Continue.
  3. At the command prompt, type the following, commands and then press ENTER after each command.

        net stop wuauserv
        net stop bits

        net stop cryptsvc

  1. Please do not close the Command Prompt window.

 Renaming folders pertaining to Windows Update

  1. At the command prompt, type the following commands, and then press Enter after each command:
  2. ren %systemroot%\\\\System32\\\\Catroot2 Catroot2.old
  3. ren %systemroot%\\\\SoftwareDistribution SoftwareDistribution.old
  4. Please do not close the Command Prompt window.

Registering DLL’s pertaining to Windows Update

  1. Please copy and paste the following text into a new Notepad document, and save the file as WindowsUpdate.BAT
  2. If saved correctly the icon will change from a Notepad file to BAT file which has two blue cogs as its icon.


  1. You can manually type each command at the command prompt:

regsvr32 c:\\\\windows\\\\system32\\\\vbscript.dll /s

regsvr32 c:\\\\windows\\\\system32\\\\mshtml.dll /s

regsvr32 c:\\\\windows\\\\system32\\\\msjava.dll /s

regsvr32 c:\\\\windows\\\\system32\\\\jscript.dll /s

regsvr32 c:\\\\windows\\\\system32\\\\msxml.dll /s

regsvr32 c:\\\\windows\\\\system32\\\\actxprxy.dll /s

regsvr32 c:\\\\windows\\\\system32\\\\shdocvw.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups2.dll /s

regsvr32 wups.dll /s

regsvr32 wuweb.dll /s

regsvr32 Softpub.dll /s

regsvr32 Mssip32.dll /s

regsvr32 Initpki.dll /s

regsvr32 softpub.dll /s

regsvr32 wintrust.dll /s

regsvr32 initpki.dll /s

regsvr32 dssenh.dll /s

regsvr32 rsaenh.dll /s

regsvr32 gpkcsp.dll /s

regsvr32 sccbase.dll /s

regsvr32 slbcsp.dll /s

regsvr32 cryptdlg.dll /s

regsvr32 Urlmon.dll /s

regsvr32 Shdocvw.dll /s

regsvr32 Msjava.dll /s

regsvr32 Actxprxy.dll /s

regsvr32 Oleaut32.dll /s

regsvr32 Mshtml.dll /s

regsvr32 msxml.dll /s

regsvr32 msxml2.dll /s

regsvr32 msxml3.dll /s

regsvr32 Browseui.dll /s

regsvr32 shell32.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups.dll /s

regsvr32 wuweb.dll /s

regsvr32 jscript.dll /s

regsvr32 atl.dll /s

regsvr32 Mssip32.dll /s

 Restarting services pertaining to Windows Update

  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
  2. If you receive a notification from User Account Control simply click Continue.
  3. At the command prompt, type the following, commands and then press ENTER after each command.

        net start wuauserv
        net start bits

        net start cryptsvc


After this Vista SP1 installed from Windows Update.

How to create a User-Defined Service

How To Create a User-Defined Service

Article ID: 137890 - View products that this article applies to.
System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center
This article was previously published under Q137890
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to do this, view the \"Restoring the Registry\" or the \"Restoring a Registry Key\" online Help topics in Registry Editor.


The Windows NT Resource Kit provides two utilities that allow you to create a Windows NT user-defined service for Windows NT applications and some 16-bit applications (but not for batch files). 

Instrsrv.exe installs and removes system services from Windows NT and Srvany.exe allows any Windows NT application to run as a service.


To create a Windows NT user-defined service, perform the following steps: 
  1. At a MS-DOS command prompt(running CMD.EXE), type the following command:

    path\\INSTSRV.EXE My Service path\\SRVANY.EXE

    1. path is the drive and directory of the Windows NT Resource Kit (i.e., C:\\RESKIT) and My Service is the name of the service you are creating.


    C:\\Program Files\\Resource Kit\\Instsrv.exe Notepad C:\\Program Files\\Resource Kit\\Srvany.exe
    NOTE: To verify that the service was created correctly, check the registry to verify that the ImagePath value under
    HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\service name
    is set to point to SRVANY.EXE. If this is not set correctly, the service will stop shortly after it starts and return an Event ID 7000 \"The service name failed to start.\" 

    WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

    For information about how to edit the registry, view the \"Changing Keys And Values\" online Help topic or the \"Add and Delete Information in the Registry\" and \"Edit Registry Data\" online Help topics in Registry Editor.

    NOTE: You should back up the registry before you edit it.

  2. Run Registry Editor (Regedt32.exe)and locate the following subkey:

    HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\<My Service>

  3. From the Edit menu, click Add Key. Type the following and click OK:

    Key Name: Parameters
    Class : <leave blank>

  4. Select the Parameters key.
  5. From the Edit menu, click Add Value. Type the following and click OK:

    Value Name: Application
    Data Type : REG_SZ
    String : <path>\\<application.ext>

    where <path>\\<application.ext> is the drive and full path to the application executable including the extension (i.e., C:\\WinNT\\Notepad.exe)

  6. Close Registry Editor.
By default, a newly created service it configured to run Automatically when the system is restarted. To change this setting to Manual, run the Services applet from Control Panel and change the Startup value to Manual. A service set to Manual can be started in one of several ways: 
- From the Services applet in Control Panel 

- From a MS-DOS command prompt, type the following: 

NET START <My Service> 

- Use the Sc.exe utility from the Resource Kit. Type the following from a MS-DOS command prompt: 

<path>\\Sc.exe start <My Service> 

where <path> is the drive and directory of the Windows NT Resource Kit (i.e., C:\\Reskit).

For more information on installing and removing a user-defined service, please see the Srvany.wri document provided with the Windows NT Resource Kit utilities (i.e., C:\\Reskit\\Srvany.wri). This document can also be found on the Windows NT Resource Kit CD in the Common\\Config directory.