Recorded live at Lone Fir Cemetery Studios in Portland, OR.
http://lcwmusic.bandcamp.com/
David Lamkins – Guitar
Stephen Caird – Bass & Cello
Joe Williams – Drums
Recorded live at Lone Fir Cemetery Studios in Portland, OR.
http://lcwmusic.bandcamp.com/
David Lamkins – Guitar
Stephen Caird – Bass & Cello
Joe Williams – Drums
Sunset Strip
God I hate printers.
I’ve been fighting a Konica with a Fiery for the last week or so. I think I have it figured out. My problems started when I was adding some users to the scanning function via the web interface and another user power-cycled the printer. When I’m doing the administrative work the printer appears off-line. The user couldn’t print; reboot that sucker.
It was shortly after the printer reboot that we started having issues stapling and secure printing. The stapling option wasn’t available and secure print just wouldn’t work. I screwed around for a couple of days – mostly hoping the thing fixed itself. It didn’t. I called for help; I hate asking for help
The printer experts said to update the driver on the server. After doing that users were getting a “LoadLibraryEx / jppath” error when viewing properties. “Don’t view the properties!” you might say. And that’s exactly what I said but people wanted to staple, duplex, print in color. . .Users! Amirite? The driver on the workstation wasn’t updating properly. How do you completely delete a driver from a workstation?
To remove a print driver from a workstation:
In Devices and Printers, delete the printer
Select another printer and on the menu bar click the Print server properties menu item
The Print Server Properties window will open
Click Ports and delete the port the deleted printer was using
Click Drivers, select the driver to delete, and click Remove, select Remove driver and driver package, and click OK
Click Yes in the warning window.
I didn’t know that Print Server Properties screen was there. Nice stuff, but what if that doesn’t work? I had a couple computers that wouldn’t allow the drivers to be deleted. What then?
Stop the Print Spooler
In Regedit look for the print processors (Windows 8.1 below, 7 and XP are in similar, but not exact, locations):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Print Processors\
Rename those suckers but remember the old names (maybe do something simple like add a .old to the end)
Restart the spooler
Try deleting the driver again (see steps above)
Stop the spooler
Return the print processors to their original names
Restart the spooler
That’s it! Reinstall the driver and start printing.
My users’s problems went away but no one was able to explain to me why replacing the driver on the server was the fix. Things are working but it’s a bit unsatisfying. I hate printers.
A few handy PowerShell commands I just don’t use often enough to remember:
Change a users password
Set-MsolUserPassword -UserPrincipalName username@domain.com -NewPassword Password1 -ForceChangePassword $false
Hide a user from the address book
Set-Mailbox -Identity username -HiddenFromAddressListsEnabled $true
Add Rights to a Public Folder
Add-PublicFolderClientPermission -Identity “\folder name” -AccessRights Editor -User username
Add an Address to an Account
set-Mailbox username -EmailAddress @{add=“address@something.com”}
Did it work?
get-Mailbox username | fl EmailAddresses
SPAM!
What is the user currently allowing?
get-MailboxJunkEmailConfiguration -identity username | select -expandproperty TrustedSendersAndDomains
Add something to WhiteList
set-MailboxJunkEmailConfiguration -identity username -TrustedSendersAndDomains @{Add=”domain.com”}
Block a sender for a particular user
$Temp = Get-MailboxJunkEmailConfiguration -Identity username
$Temp.BlockedSendersAndDomains += “domain.com”,”user@domain.com”
Set-MailboxJunkEmailConfiguration -Identity username -BlockedSendersAndDomains $Temp.BlockedSendersAndDomains
Or an easier way. . .
Set-MailboxJunkEmailConfiguration -Identity username -BlockedSendersAndDomains @{Add=”domain.com”}
Count and Delete Calendar Items
Search-Mailbox –identity username –SearchQuery kind:meetings –EstimateResultOnly
Search-Mailbox –identity username –SearchQuery kind:meetings –DeleteContent
Calendar Permissions
Of course these would work with any folder and yes, I could teach the user how to do this themselves, but they do it less frequently than I do; this is just easier.
List the current permissions on the Calendar
get-mailboxfolderpermission -Identity username:\calendar
Add permissions
(use set-mailboxfolderpermissions to change)
add-mailboxfolderpermission -Identity username:\calendar -user otheruser -accessrights Editor
Delete/remove Permissions
remove-mailboxfolderpermission -Identity username:\calendar -user otheruser -confirm:$false
The world breaks everyone, and afterward, some are strong at the broken places.
The best way to find out if you can trust somebody is to trust them.
But a man is not made for defeat. A man can be destroyed but not defeated.
#####
Ernest Hemingway – and in the end he was broken, destroyed, and defeated.
An event log had a disk error this morning indicating something wrong with LogicalDisk(HarddiskVolume2). What the heck drive letter is that anyway? SysInternals to the rescue:
https://technet.microsoft.com/en-us/sysinternals/bb896657.aspx
WinObj shows this and all sorts of other juicy stuff from the NT Object Manager’s name space.
Sandstone Clinic