Absolutely. I'm sure I've mentioned this before, but Lucy Kellaway's series of office spaces are great. Like this Lego one

Youtube Video

@momurda said in Security Incident Response:

Yes i was thinking they just want an answer and dont really care what the answer is.

Good chance that that is the case.

+1 for primary application platform on Ubuntu.

If you mean what I think you mean, I use Centos for General server stuff, basically a server that can handle anything or can be more than 1 thing, however for Ubuntu and cause of the snaps, I use Ubuntu for specific roles like :

File server
Or
RockChat server

For specific purpose roles.

I just write an article about that here: http://www.francescoprovino.com/2017/04/16/full-disk-encryption-unlocking-from-virtual-serial-tty-paranoia-xenserver-and-libvirt/ .

I have had a Mushkin and a Crucial. Both seemed fine.

@msff-amman-Itofficer @stacksofplates

Got more usefull info, it seems it is cause of my -c switch:

https://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html

Convert

The convert option is used to convert one recognized image format to another image format.
Command format:

qemu-img convert [-c] [-f format] [-o options] [-O output_format] filename output_filename

Convert the disk image filename to disk image output_filename using format output_format. The disk image can be optionally compressed with the -c option, or encrypted with the -o option by setting -o encryption. Note that the options available with the -o parameter differ with the selected format.

Only the qcow2 format supports encryption or compression. qcow2 encryption uses the AES format with secure 128-bit keys. qcow2 compression is read-only, so if a compressed sector is converted from qcow2 format, it is written to the new format as uncompressed data.

Image conversion is also useful to get a smaller image when using a format which can grow, such as qcow or cow. The empty sectors are detected and suppressed from the destination image.

@NashBrydges Oh this is awesome! Gonna be giving that a go on Monday or Tuesday.

@scottalanmiller said in FreePBX Send Mail Error on Vultr:

@JaredBusch said in FreePBX send mail error:

Did you request smtp be unblocked by vultr?

It's blocked by default, so if you forget to request this on any server, outbound emails won't work.

The block is account level. Not per server.

Thank you, I'll investigate from here.

@NerdyDad said in Creating users:

Try this out. It pops up with a command prompt to ask you a few questions to get started. Once the questions are answered, it takes care of most everything else. When it is done, it should spit out a piece of paper for you to give to the new employee with the information that they need.

I sterilized it so that you could use it in your company.

#Imports the AD & NTFS Modules (Module 1.02) Import-Module activedirectory Import-Module MSOnline #Sets Variables (Module 1.03) $fn #First Name $ln #Last Name $title $dep #Department $loc #Location $man #Manager $un #Username $officePhone $streetAdd $city $ZIP $fi #First Name Initial, will be used to figure out Username #Getting information (Module 1.04) Write-Host "I need some information from you first. Answer the following questions to get started." $fn = read-host "First Name?" $ln = Read-Host "Last Name?" $title = Read-Host "Title?" $dep = Read-Host "Department?" $man = Read-Host "Manager (Username)?" $loc = Read-Host "<location>?" #Finding out the Username (Module 1.05) $fi = $fn.Substring(0,1) $un = -join ($ln, $fi) #Sets Location information (Module 1.06) if ($loc -eq "Loc1") { #If the user is in Loc1 (Module 1.07) $officePhone = "(999) 999-9999"; $streetAdd = "123 Anywhere Drive"; $city = "YourTown"; $ZIP = "12345"; } Else { #If the user is in Loc2 (Module 1.08) $officePhone = "(987) 654-3210"; $streetAdd = "987 Nothere Blvd"; $city = "Somewhere Else"; $ZIP = "98765"; } #Sets Password (Module 1.09) $passwd = (Read-Host -AsSecureString "Account Password") $password = ConvertFrom-SecureString -SecureString $passwd $userParams = @{ #(Module 1.10) 'Name' = $un; 'Enabled' = $true; 'AccountPassword' = $passwd; 'UserPrincipalName' = -join ($un, "@mycompany.com"); 'SamAccountName' = $un; 'ChangePasswordAtLogon' = $false; 'GivenName' = $fn; 'Surname' = $ln; 'DisplayName' = -join ($fn, " ", $ln); 'Description' = $title; 'OfficePhone' = $officePhone; 'StreetAddress' = $streetAdd; 'City' = $city; 'State' = "Texas"; 'PostalCode' = $ZIP; 'Title' = $title; 'Department' = $dep; 'Company' = 'MyCompany'; 'Manager' = $man; } #Creates the user in AD (Module 1.11) New-ADUser @userParams #Wait for the account to be created before doing anything else (Module 1.12) Start-Sleep -Seconds 10 #Makes the user's network drive, scan folder, and sets the permissions to their folders and files (Module 1.13) if ($loc -eq "Loc1") { #If the user is in Loc1 (Module 1.14) New-Item -Name $un -ItemType directory -Path "\\server\folder\" #Creates users network drive New-Item -Name scans -ItemType directory -Path "\\server\folder\$un\" #Creates users scan folder } Else { #If the user is in Loc2 (Module 1.15) New-Item -Name $un -ItemType directory -Path "\\server\folder\" #Creates users network drive New-Item -Name scans -ItemType directory -Path "\\server\folder\$un" #Creates users scan folder } #Adds the user to the correct Security Group for permissions and other network drives if ($dep -eq "Accounting"){ #(Module 1.16) Add-ADGroupMember -Identity 'Accounting' -Members $un #(Module 1.17) } #Adds the user to the Accounting Group Elseif ($dep -eq "Customer Service") { #(Module 1.18) Add-ADGroupMember -Identity 'Customer Service' -Members $un #(Module 1.19) } #Adds the user to the Customer Service Group Elseif ($dep -eq "Executives") { #(Module 1.20) Add-ADGroupMember -Identity 'Executives' -Members $un #(Module 1.21) } #Adds the user to the Executives Group Elseif ($dep -eq "HR") { #(Module 1.22) Add-ADGroupMember -Identity 'Human Resources' -Members $un #(Module 1.23) } #Adds the user to the Human Resources Group Elseif ($dep -eq "Human Resources") { #(Module 1.24) Add-ADGroupMember -Identity 'Human Resources' -Members $un #(Module 1.25) } #Adds the user to the Human Resources Group Elseif ($dep -eq "IT") { #(Module 1.26) Add-ADGroupMember -Identity 'Domain Admins' -Members $un #(Module 1.27) } #Adds the user to the Domain Admins Group for IT Elseif ($dep -eq "Maintenance") { #(Module 1.28) Add-ADGroupMember -Identity 'MaintGroup' -Members $un #(Module 1.29) } #Adds the user to the Maintenance Group Elseif ($dep -eq "Production") { #(Module 1.30) Add-ADGroupMember -Identity 'Production' -Members $un #(Module 1.31) } #Adds the user to the Production GroupHR Elseif ($dep -eq "QA") { #(Module 1.32) Add-ADGroupMember -Identity 'QA Group' -Members $un #(Module 1.33) } #Adds the user to the QA Group Elseif ($dep -eq "Quality Assurance") { #(Module 1.34) Add-ADGroupMember -Identity 'QA Group' -Members $un #(Module 1.35) } #Adds the user to the QA Group Elseif ($dep -eq "Shipping") { #(Module 1.36) Add-ADGroupMember -Identity 'SHIP' -Members $un #(Module 1.37) } #Adds the user to the Shipping Group Else { #(Module 1.38) Add-ADGroupMember -Identity 'Domain Users' -Members $un #(Module 1.39) } #Dumps the user to the Domain Users Group $manfn = Get-ADUser $man -Properties Name | select Name #Gets the manager's name (Module 1.40) #Creates a report of the User's information $report = "Hello $fn $ln, From the IT Department, welcome to <MyCompany>. We are here to help you connect to the resources that you need for your job. If you need assistance with technology, please feel free to contact us at either the help page, which is set as your home page in Internet Explorer, email us at helpdesk@<MyCompany>.com, or call us at extension 4357. Below you will find your information so that you can login to the network and get started: Your username is domain\$un Your password is Your email address is $fn$ln@<MyCompany>.com Your phone number is $officePhone Ext. It is suggested that you change your password to something that you can remember but difficult enough that somebody else cannot figure out. The requirement is only 6 characters, but we do advise on making it longer, throw some numbers and special characters in there as well to make it stronger. Best advice would be to use a pass-PHRASE instead of a pass-WORD. Your computer should already be setup with your email loaded and your network drives. At <MyCompany>, we use Microsoft Outlook as the email client. Depending on what department you are in will depend on what drives you have available. Generally, everybody will have an F: drive and a G: drive. The F: drive is your network folder. Place in there the documents that you feel you cannot do your job without. In the F: drive will be a scan folder. When you go to the Xerox to scan in documents, then you will find them in your scan folder. The G: drive is a company-wide shared folder. As for your department drives, it would be best to talk with $($manfn.name), your supervisor/manager, about the nature and uses of these drives. The use of the equipment and resources provided are a privilege to you for use and should not be taken advantage of. There are measures set in place that allows us to manage the network. Do not assume that there is any personal privacy on this network. The only privacy that you can assume is for the nature of your work. All information (including emails, documents, spreadsheets, pictures, etc.) contained on the equipment provided and on the network is the sole property of Standard Meat Company. If you have problems with your equipment or network resources, please feel free to ask. We do not mind helping, but we cannot help if we do not know, so please ask! Sincerely, Your IT Department" if ($loc -eq "Loc1") { #(Module 1.43) Write-Output $report | Out-Printer } Else { #(Module 1.44) Write-Output $report | Out-Printer \\server\'Xerox WorkCentre 4260' } #Waiting for AD & Azure to Synchronize, which synchronizes every 30 minutes (Module 1.45) Write-host "Waiting..." Start-Sleep -Seconds 1800 #Connect to O365 and licenses the user Connect-MsolService #(Module 1.46) Set-MsolUserLicense -UserPrincipalName (-join($un,'@<MyCompany>.com')) -AddLicenses #(Module 1.47) #Connects to the Exchange box, creates the users email account, then disconnects from the Exchange box $mail = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -AllowRedirection -Authentication Basic -Credential $cred #(Module 1.48-Part 1) Import-PSSession $mail -WarningAction SilentlyContinue | Out-Null #(Module 1.48-Part 2) enable-Mailbox -Identity $un -Alias $un -DisplayName (-join($fn,$ln)) #Creates the users mailbox (Module 1.49) IF ($dep -eq "Executives") { #(Module 1.50) Set-Mailbox (-join($un,'@<MyCompany>.com')) -ProhibitSendQuota 19.5GB -ProhibitSendReceiveQuota 20GB -IssueWarningQuota 19GB #Sets the mailbox size in Exchange Online so that the user isn't using all 50 GB of storage (Module 1.51) } #If they are an executive, then they get 20 GB of mailbox space elseif ($dep -eq "IT") { #(Module 1.52) Set-Mailbox (-join($un,'@<MyCompany>.com')) #(Module 1.53) } #IT gets the full mailbox, of course else { #(Module 1.54) Set-Mailbox (-join($un,'@<MyCompany>.com')) -ProhibitSendQuota 9.5GB -ProhibitSendReceiveQuota 10GB -IssueWarningQuota 9GB #Sets the mailbox size in Exchange Online so that the user isn't using all 50 GB of storage (Module 1.55) } #Otherwise, everybody else gets 10 GB of mailbox space Remove-PSSession -Session $mail #Disconnects from the Exchange box (Module 1.56)

This is a great script, especially if you have users frequently cycling in and out of the company. Also a good base to expand from, or customize to make it fit many environments.

Something that stuck out in the script for me was that the homeDirectory AD attribute wasn't being used (unless I missed it). When you set that, AD automatically does permissions appropriately for the users home drive or home directory. It works well with DFS or DFSR.

Edit: I use the following format for "homeDirectory": \\DOMAIN\Namespace\HomeDrives\%username%
Path can be whatever works, above is just what happens to be for that case.

@JaredBusch said in Office365 Domains:

Use your real domain for the log you don't use the on Microsoft otherwise everything will have to get changed or just have problems in the future

The only issues I had was getting the iPhone to connect. But I figured out if I just put in the wrong password, I can then edit the server to the correct O365 entry.

MDaemon requires autodiscover to work at all so I have to leave it be for now.

Also had to make entries to the registry to get Outlook to work, but that seems to be working fine with the registry changes.

@BBigford awesome!

@dafyre said in Best CA for SSL Certificates:

@IRJ said in Best CA for SSL Certificates:

This line on GitHub about the project makes me even more weary:

Time spent on developing Certify is extremely limited. If you have a bug or feature and you can fix the problem yourself please just:

File a new issue
Fork the repository
Make your changes
Submit a pull request, detailing the problem being solved and testing steps/evidence
If you cannot provide a fix for the problem yourself, please file an issue and describe the fault with steps to reproduce. General issues which cannot be easily reproduced are likely to be ignored, sorry!

At least they're up front about expectations.

And the rest of it's just boilerplate submit an issue

Nice new feature, looking forward to rolling that out.

Legal is really all about "common sense" and following good practices. Think of it as having to defend your decisions logically, rather than following a specific guideline or rulebook.

That is alot but with the recent patches by Microsoft I should not be surprised.

Yes, those errors will concern me a lot. Usually I have seen this error on Synology with failing hardware parts as replacing the drive sometimes do not fix the issue nor a firmware update. Contact Synology support to have them check the device.

Cool. They seem to have really come through.