Liquidware Labs Acquires Entrigue Systems Learn More

Script Start ProfileUnity 2.3 released. Please see the change log for further details.

Entrigue Launches Script Start ProfileUnity at VMworld Learn More

More News & Updates

Script Start Architecture

Script Start Setup

	1.	Install Script Start
		The Script Start Installer will guide you through the setup of both the Script Start Management Console and the Script Start Client. Installation is straightforward and merely requires an administrator to answer a few simple prompts. The Script Start Installer can be downloaded here.

	2.	Build and Download Configuration
		Enter the details about your network layout and desired configuration using the Script Management and Filter Management menu options located in the Management Console. When you have finished entering your details, download the configuration file to the ScriptStart folder located in the netlogon share on your domain controller.

	3.	Assign
		User accounts need to have Script Start assigned as their logon script. The mechanism used to assign Script Start to a user account is dependent upon your domain controller infrastructure. Active Directory Domain Infrastructure Create a Group Policy with the following two settings: 1) Assign compat.vbs as a startup script. View Example 2) Assign cache.vbs as a logon script. View Example Note: You will need to replace "entrigue.net" in the above examples with the name of your domain. Windows NT Domain Infrastructure Open User Manager for Domains, select the user account, choose profile, and simply fill in the Logon Script Name field. View Example SAMBA Domain Infrastructure SAMBA has the ability to assign logon scripts to all users globally. To employ this feature and assign Script Start to all users at once, simply edit your smb.conf configuration file and enable the logon script option. The relevant portion of smb.conf is shown below.

Script Start Execution

	4.	User Logon
		During user logon, the Script Start Client is automatically downloaded to the target machine.

	5.	Script Start Execution
		The Script Start Client executes and applies your configuration. Script Start executes in the security context of the user logging on to the network. Privileges are never elevated during execution, insuring your security policies are preserved.

System Requirements

Script Start Client The Script Start Client is dependent on a Microsoft domain infrastructure. Either a Microsoft domain controller or a server running domain controller emulation software, such as SAMBA, is required. The Script Start Client supports machines running Windows 95, Windows 98, Windows ME, Windows NT 4.0, Windows 2000, Windows XP, Windows 2003, Windows Vista, Terminal Server, and Citrix Presentation Server. Machines running the Script Start Client must be members of the domain. The Script Start Client officially supports domain controllers running Windows NT 4.0, Windows 2000, Windows 2003, and SAMBA using tdbsam or ldapsam as the password backend. Script Start Management Console The Script Start Management Console can be installed on a machine running Windows 2000, Windows XP, Windows 2003, Windows Vista, or Linux. If necessary, the Management Console can be installed on a domain controller. The automated installation package supports Windows 2000 and newer. Linux installations require Apache/PHP/PostgreSQL to be installed manually.