How to configure WSAM for Windows Drive Mapping By Ravi Vinukonda

How to configure
WSAM for Windows
Drive Mapping
By Ravi Vinukonda
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
1
First, ensure that you have the SAM license installed
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
2
Enable WSAM for an IVE role
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
3
Enable WSAM
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
4
Configure WSAM Application properties
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
5
Configure WSAM Application properties
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
6
Configure WSAM Application properties - Add Standard Application
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
7
Configure WSAM Application properties - ADD “NETBIOS FILE
BROWSING”
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
8
Configure WSAM Application properties
Copyright © 2005 Juniper Networks, Inc.
-Add Servers list
Proprietary and Confidential
www.juniper.net
9
Configure WSAM Application properties – Server NetBIOS name or ip
address AND tcp port
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
10
Configure WSAM Application properties – Server NetBIOS name
or ip address AND tcp port
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
11
Configure WSAM session options
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
12
Configure WSAM session options – Auto Launch and Auto upgrade
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
13
Configure IVE Resource policies for SAM
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
14
Configure IVE Resource policies for SAM
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
15
Configure IVE Resource policies for SAM – New policy
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
16
Configure IVE Resource policies for SAM
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
17
End User Experience – WSAM installation and Reboot Alert
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
18
End User Experience – Launching WSAM session after reboot
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
19
End User Experience – Map network Drive
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
20
Congratulations.
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
21
WSAM Supported platforms: OS Service Package version 5.0
ƒ
Windows XP: Internet Explorer 6.0
ƒ
Windows XP SP2*: Internet Explorer 6.0
ƒ
Windows 2000: Internet Explorer 5.5 SP2 and Internet Explorer 6.0
ƒ
Windows XP SP2*: Firefox 1.0
ƒ
Windows 2000: Firefox 1.0
ƒ
Windows 98 SE: Internet Explorer 6.0
ƒ
WSAM + NetBIOS is not supported in Windows 98
ƒ
Windows ME: Internet Explorer 6.0
ƒ
WSAM + NetBIOS is not supported in Windows ME
* To use J-SAM, W-SAM, or Terminal Services with Windows XP SP2, the XP SP2 Hot
Fix
(http://support.microsoft.com/default.aspx?scid=kb;en-us;884020) is required. Refer
to the Juniper Networks
Support Site (http://www.juniper.net/support) for more details.
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
22
Known Issues
ƒ If an administrator configures W-SAM with NetBIOS support, once a user installs W-SAM, they
are prompted to reboot their PC before continuing. If they do not reboot, W-SAM does not
function correctly
ƒ To access a windows file share by hostname using W-SAM, the administrator must explicitly
configure the server’s NetBIOS name (alphanumeric string up to 15 characters)
ƒ Users must launch drive maps through WSAM in one of the following ways:
ƒ - NetUse--At the Command prompt, type: net use * \\server\share /user:username
ƒ - Right Click on My computer -> Map network Drive, or Explorer-enabled drive mapping.
ƒ - In Windows Explorer, go to Tools
username”.
Map Network Drive, then select “Connect using a different
ƒ When W-SAM is enabled with NetBIOS support, the presence of an installed VPN client can
cause unexpected behavior. A common symptom is that NetBIOS connections work using IP
addresses but not using hostnames. This issue is generally resolved by releasing and renewing the
IP bindings (e.g. using ipconfig). Some extreme cases might require the VPN client to be
uninstalled.
ƒ On Windows 2000 and Windows XP systems, drive mapping through W-SAM is not supported if
the users log into a domain (when logging into their PC). If this occurs, the user should see one of
the following error messages: “No Windows NT or Windows 2000 Domain Controller is available
for…” or “There are currently no logon servers available to service the logon request.” This is
caused by Windows 2000 behavior which causes domain credentials to be cached. To work around
this issue, please have the users log into their PC as a local or workgroup user or use ‘net use’ at
the command prompt.
Copyright © 2005 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
23