Going beyond the basics, webNetwork is integrated and managed through objects in directory services. This leverages your user directory, enables a single sign-on for Web resources and makes management easier than a snap-in console to MMC (Microsoft Management Console). For resources outside the directory and webNetwork, there's a "lockbox" that stores and manages IDs and passwords for legacy systems. WebNetwork also can bring together published documents from all your HTTP sites, Internet file services like CIFS (Common Internet File System), FTP and even NetWare file systems through NetWare Java Client libraries.
Spelunking With Apps
I created a virtual private host (VPH) object in the directory to represent a terminal services (TS) host behind the relay server. The VPH object contains the DNS name or IP address of the destination server, the services port (3389) and the port used by the local client when connecting to the host (3389). It also contains the shortcut information for the TS application. The shortcut's command line can support switches to pass to the local application. Once the VPH object is in the directory, you create a link object to put it on the users' desktops.
Link objects restrict their associated resources to users, groups and other directory objects, such as a specific server running the Relay service. I restricted the TS link object to administrators' desktops and limited it to run through the server hosting the relay services.
To test my VPC, I logged on to the webNetwork and my personalized desktop. From an Additional Links tab, I selected the TS link.
Discover the benefits of scalable backbone and network services for application and cloud providers.
Network automation is gaining momentum. Here's how you can drive this powerful technology to its full potential.
Subsea cable alternatives can provide a level of comfort for those concerned about disruptions. Realistically, they will continue to play a small, but critical role in the short term.
