<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>smtp settings &#8211; Blue Lance</title>
	<atom:link href="https://bluelance.com/docs-tag/smtp-settings/feed/" rel="self" type="application/rss+xml" />
	<link>https://bluelance.com</link>
	<description></description>
	<lastBuildDate>Tue, 02 Jun 2026 23:10:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://bluelance.com/wp-content/uploads/2025/11/fevicon-ic-1.png</url>
	<title>smtp settings &#8211; Blue Lance</title>
	<link>https://bluelance.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Access Web Portal</title>
		<link>https://bluelance.com/docs/initial-configuration-checklist/</link>
		
		<dc:creator><![CDATA[peter thomas]]></dc:creator>
		<pubDate>Thu, 28 May 2026 16:18:18 +0000</pubDate>
				<guid isPermaLink="false">https://bluelance.com/?post_type=docs&#038;p=15837</guid>

					<description><![CDATA[After completing installation and verifying that all services are running, complete the following steps before going live. This checklist ensures LT Auditor MP is properly configured to collect data, send alerts, and support your team&#8217;s day-to-day operations. 1. Change the default admin password Log in to the Web UI and immediately change the default administrator [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">After completing installation and verifying that all services are running, complete the following steps before going live. This checklist ensures LT Auditor <sup>MP</sup> is properly configured to collect data, send alerts, and support your team&#8217;s day-to-day operations.</p>



<p class="wp-block-paragraph"><strong>1. Change the default admin password</strong> Log in to the Web UI and immediately change the default administrator password to a strong, unique password.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → User Management</strong></li>



<li>Select the admin account</li>



<li>Click <strong>Change Password</strong></li>



<li>Enter and confirm a new password</li>



<li>Click <strong>Save</strong></li>
</ol>



<p class="wp-block-paragraph"><strong>2. Configure SMTP for email alerts</strong> Set up email delivery so that alerts and scheduled reports can be sent to your team.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → SMTP Settings</strong></li>



<li>Enter your mail server details:
<ul class="wp-block-list">
<li><strong>SMTP Host</strong></li>



<li><strong>Port</strong></li>



<li><strong>Authentication credentials</strong></li>



<li><strong>From address</strong></li>
</ul>
</li>



<li>Send a test email to confirm delivery</li>



<li>Click <strong>Save</strong></li>
</ol>



<p class="wp-block-paragraph"><em>[Your administrator should fill in the specific SMTP server details for your environment.]</em></p>



<p class="wp-block-paragraph"><strong>3. Install and connect modules</strong> Install the relevant modules for your environment and confirm they are sending data to the LT Auditor <sup>MP</sup> server. Refer to each module&#8217;s dedicated documentation section for full instructions.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>Module</strong></td><td><strong>Data Source</strong></td></tr><tr><td>EventLogCentral</td><td>Windows Event Logs &amp; NTFS file activity</td></tr><tr><td>PowerShell Orchestrator</td><td>Active Directory &amp; Entra ID assessments</td></tr><tr><td>PII Scanner</td><td>Sensitive data on Windows &amp; Linux systems</td></tr><tr><td>EntraConnector</td><td>Azure sign-in &amp; Entra ID audit logs</td></tr><tr><td>NSS Module</td><td>OES NSS file activity</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><strong>4. Configure monitored scopes</strong> Define which servers, directories, and systems LT Auditor <sup>MP</sup> should monitor.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Configure → Environments</strong></li>



<li>Add each environment relevant to your deployment (Windows, Linux, eDirectory, etc.)</li>



<li>Define log categories and operations to capture within each environment</li>



<li>Save your configuration</li>
</ol>



<p class="wp-block-paragraph"><strong>5. Set up alert rules</strong> Configure at minimum a basic set of alert rules to notify your team of critical events. See the Configuring Alert Rules article for full instructions.</p>



<p class="wp-block-paragraph">Recommended starting alerts:</p>



<ul class="wp-block-list">
<li>Failed login threshold exceeded</li>



<li>Privileged account changes</li>



<li>File deletion on sensitive directories</li>



<li>New admin account created</li>
</ul>



<p class="wp-block-paragraph"><strong>6. Configure data retention policy</strong> Set how long audit data is retained in the database to manage storage and meet compliance requirements.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → Retention Settings</strong></li>



<li>Set the retention period in days</li>



<li>Click <strong>Save</strong></li>
</ol>



<p class="wp-block-paragraph"><strong>7. Set up user roles and access</strong> Create user accounts and assign appropriate roles for your team before sharing access to the platform.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → User Management</strong></li>



<li>Add user accounts for each team member</li>



<li>Assign roles based on responsibilities (admin, analyst, report viewer, etc.)</li>



<li>Save all changes</li>
</ol>



<p class="wp-block-paragraph"><strong>8. Test an alert end-to-end</strong> Before going live, confirm that the full alert pipeline is working correctly.</p>



<ol class="wp-block-list">
<li>Trigger a test event that matches one of your alert rules</li>



<li>Confirm the alert appears in <strong>Alerts → Active Alerts</strong></li>



<li>Confirm the alert notification email is received</li>



<li>Resolve the test alert</li>
</ol>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
