because there is no additional setting that i have to do with other computers, only setup MS office and everything is OK except with these 2 computers and maybe the number will increase in the future,
This one looks like it might work, but it still has a battery connector even though it's flash based.
"flash backed" means it'll store the contents of it's ram to flash when it goes to battery power, or am I missing something again?
Well that would make sense, but then Scott's early comment about NVRAM vs VolRAM wouldn't be correct, I wouldn't think - would they have three different options?
import-module ActiveDirectory
cls
write-output "This script adds the destination user to all the Groups which the source user is memberof."
write-output " "
write-output " "
$SName = Read-Host "Please Enter the alias name of the source user "
$DName = Read-Host "Please Enter the alias name of the Destination user "
$DN = Get-ADUser $DName -Server DOMAINBDC
$K = Get-ADUser -Identity $SName -Properties memberOf
foreach($group in $K.memberof)
{
Add-ADGroupMember -Identity $group -Member $DN
write-output $group
}
I've worked with multiple companies that had the opposite issue, all of their equipment control software ran on Solaris on Sparc only. So they had to maintain proprietary hardware and Solaris for everything.
I'm sure this goes against every best practice, but when I'm doing a bunch of admin stuff i issue a sudo bash and open up a new bash shell with sudo privileges
Not uncommon, and I do that a bit too (I use sudo -i su) but one of the good things about that is that it still tracks your user, it does not treat you as root for auditing.
I use it all the time. Snapshots are awesome. I've just never needed to use multiple disks and didn't think of the above scenarios when you would have multiple PVs.