Thought I came up with a good one, but Na.
Best posts made by Danp
-
RE: Sodium's new name! Looking for some input!
-
Virtualization build
Recently got a quote for the following used server --
Dell R720 SFF Dual E5-2670 8 core 2.5 Ghz 192 GB RAM 8x New Samsung 480GB SSD H710 integrated LSI SAS RAID 0-6 16 drive Bay server Dual 750W power supply Rail kit 1 year warranty
Quoted price was $2629/ea. The plan would be to replace my aging R905 with two newer servers.
Comments or suggestions?
-
RE: Ideas for how to use new, free gear from HPE?
Maybe use the new equipment in production and turn your existing production equipment into your test environment?
Latest posts made by Danp
-
RE: Options to securely deliver electronic documents?
Have you looked at zendto? I believe that is its main focus.
-
RE: Cloud Based Auto-Attendant
@DustinB3403 I used RC in the past, and it should be able to handle this without issue. You should only need to pay for a single user for this to work.
-
RE: Get Alert Whenever There is MS SQL Server Access
No idea. For fun, I asked ChatGPT and this was the response --
Yes, you can set up a notification system to receive alerts whenever a user connects to Microsoft SQL Server. One common approach is to use SQL Server Audit, which allows you to capture and log specific events in the SQL Server instance. Here's a step-by-step guide on how to set up SQL Server Audit to receive notifications for user connections: 1. Connect to your SQL Server instance using a tool like SQL Server Management Studio (SSMS). 2. Expand the "Security" folder in the Object Explorer. 3. Right-click on the "Audits" folder and select "New Audit...". 4. Provide a name for the audit, such as "User Connections Audit," and click "OK." 5. In the "Audit Destination" section, choose whether to save the audit logs to a file or the Windows Security event log. Select the appropriate option and configure the settings as desired. 6. Under the "Events" tab, click on the "Add..." button. 7. In the "Audit Action Type" window, expand the "Security" category, and select the "Audit Login" action. Click "OK" to add it to the audit. 8. Click "OK" to save the audit settings. 9. Right-click on the "Server Audit Specifications" folder and select "New Server Audit Specification...". 10. Provide a name for the audit specification, such as "User Connections Audit Specification," and select the audit you created in the previous steps. 11. Under the "Audit Action Type" window, select the "Audit Login" action. 12. In the "Object Types" section, select the "Server" object type. 13. In the "Principal Name" section, select the "Public" option to capture all logins. 14. Click "OK" to save the audit specification. Now, whenever a user connects to the SQL Server, the event will be captured by the audit and logged according to your configured settings. Depending on the destination you selected, you can set up email notifications or other alerts to be triggered whenever new audit logs are generated. Please note that setting up and managing SQL Server Audit may require administrative privileges and should be done carefully to ensure proper security and compliance practices.
-
RE: winget vs choco
Check out WingetUI, which can manage packages for choco, scoop, and winget.