My Blog: Troubleshooting

Showing posts with label Troubleshooting. Show all posts

Wednesday, October 6, 2010

“The network path was not found" error on Win XP sp3”

The problem
You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.
A solution (there could be several causes)

On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
Scroll down to the Computer Browser service.
If it is Disabled or set to Manual, set it to Automatic.
Then start it. It may stop immediately again, but this is OK.
At this point try to connect to the target machine.

If it still doesn't work, you can try the following:

open up Network Connections, under Control Panel.
Right click on your network adapter and click on Properties.
Click on Internet Protocol (TCP/IP), then click on Properties.
Click on Advanced, and click on the WINS tab.
Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
Press OK on each screen until everything's closed.
Go back to the client machine and try again.
You should be able to connect!

If it still doesn't work:

Go back to the Services window and find the service named Routing and Remote Access.
Double-click on it, set it to Manual, and stop it.
Close Services and try to connect from your client machine again.

Monday, October 4, 2010

OSD Task Sequence : Formatted the drive, dropped the image on the PC

Issue: When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers.

Looking at the SMSTS.log, the following error is logged:

Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager

Cause: This issue is caused because the "Setup windows and ConfigMgr" task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence.

The "Setup windows and ConfigMgr" task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared.

Resolution: For these reasons, the "Setup windows and ConfigMgr" task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail.

The "Setup windows and ConfigMgr" task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.

Wednesday, August 25, 2010

SCCM Client Services and applets

If SMS/SCCM Client is installed we will get SMS Agent host (ccmexec.exe ) service will be installed all the related information log file is ccmexec.log file

if client installed it will come in Control Panel

if the client OS version is 32 bit then you can find the applets in the control panel directly, if it is 64 bit OS then you will get in 32-bit Control Panel items (The reason is sccm is a 32 bit application) also client will be installed in windows\ccmsetup for client installation

and for client logs in 64 located in