Had a school that bought the cloud licensing for Adobe Acrobat DC and wanted help deploying Adobe Acrobat to the workstations on their network. Began the process by creating an MSI based package with the Adobe Cloud Packager for deployment via group policy, but the deployment failed. Found that this is a known issue with Adobe Acrobat DC and can only be solved by running a script instead:
Creating Script for Deploying Adobe Acrobat DC Cloud Edition
Open an administrative command prompt
Change directory to – [Package Location]\Exceptions\APRO15.0en_US\Adobe Acrobat\
Run the following – Setup.exe /sALL /extUI /sl “en_US” /msi INSTALLDIR=”” EULA_ACCEPT=”NO” SUITEMODE=1 OWNERSHIP_STATE=1 LANG_LIST=”en_US” INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1
Open the application then Sign In to Adobe Cloud
Paste Product Key into the prompt that opens
This was found after some deep research into the Adobe Support site. Once you have tested these line of code then a batch file can be created for deploying Adobe Acrobat DC via Group Policy.
If your company is using Adobe Acrobat DC and needs help deploying Adobe Acrobat DC to network workstations, then contact us for assistance.
Had a customer reporting that their clients receive WinMail.dat file as an attachment instead of the email that they intended. According to Microsoft Support:
The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
Two ways to stop clients receive WinMail.dat file as attachment
Either send everyone plain text emails or change the settings on a per contact basis inside of Outlook. Here is a link for how to do it on a per contact basis, this can be tricky but worth it if you want to keep the rich text formatting of email for the rest of your contacts.
If your company is using Exchange or Office 365 for email and need help troubleshooting, then contact us for assistance.
Had a client that allows a third party bookkeeper to login remotely to one of their workstations where their accounting software is installed. This user expressed that “all of a sudden” they were unable to see any desktop icons or work with the Start menu properly. Once remotely connected into the system with the bookkeeper found an error message that access to the redirected desktop was denied. Tried changing permissions on the Desktop folder, tried renaming the folder and letting a fresh login recreate them on the server, and tried renaming the local profile folder then another login to recreate those as well. Then I finally remembered the solution – it was a corrupt user profile in the registry: z
Remember to look through this list and find the user in question, export the key (aka backup) and then remove the entire folder containing their profile. One more reboot and login fixed the issue successfully. Thanks to following Microsoft TechNet Article for the details on the fix.
If your company is using remote access or have issues with a corrupt user profile, then contact us for assistance.
Had a lower level technician try to import a large Active Directory user list of incoming freshman into a high school’s Active Directory via Powershell and mistakes were made. Basically there was no UserPrincipalName created which made logon to workstations difficult. Here is the PowerShell script used to fix the issue:
Powershell Script to Import Active Directory User List
Write-Host “Changes to the user $($GivenName) $($SurName) were made!”
For ideas on how to correctly import a large number users into Active Directory, look at how to format the spreadsheet and then how to write the PowerShell script at these links.
If your company is using Active Directory User List for import or need help managing / maintaining your active directory domain, then contact us for assistance.
Had a school that reported that several computers were unable to get new IP addresses and therefore unable to logon to the domain. Their DHCP was handled by their local domain controllers with each server handling half of the /23 address space which equates to 510 total usable address for local devices on that subnet. Checked DHCP on the primary domain controller and found that their were 450+ BAD ADDRESS items in the scopes lease, so deleted these to free up space. Checked on the secondary domain controller and found that the DHCP server had a blue exclamation point on it which meant that the scopes leases were exhausted. Tried to look at the lease list and it had a red X on it and no entries listed. So how to fix this? Here is a method that I found to perform a DHCP repair / rebuild in this kind of situation:
How to Perform DHCP Repair / Rebuild
1. On the Windows DHCP server open a command prompt with administrative privileges
2. Type the following command to backup all the DHCP configurations settings:
netsh DHCP server dump>DHCPdump.txt
3. Stop the DHCP server service
4. Delete the contents of the c:\Windows\System32\DHCP folder including all subfolders.
5. Start the DHCP server.
6. In the same administrative command prompt type to restore the DHCP configuration settings:
netsh exec DHCPdump.txt
7. Then in the administrative command prompt type to run diagnostics on the DHCP scope:
netsh DHCP server initiate reconcile
8. Open up the DHCP administrator tool and check that all of the options are intact and the Reservations are present.
9. In the same administrative command prompt type to export all DHCP information to a file:
netsh DHCP server export DHCP.txt all
10. Copy this file and the DHCPdump.txt file somewhere else as a backup.
This DHCP repair worked immediately and client workstations started to register for DHCP leases again.
If your company is using Windows DHCP Servers or need help with a DHCP repair / rebuild, then contact us for assistance.
Migrated a client to a new domain for reasons that are beyond the scope of this blog post. After the migration and proper setup of Folder Redirection to the file server, several clients were reporting that their files were not the latest version. Researched the issue and found that their was no trace of the latest versions of these files on the workstation or server via Windows Search, but did find shortcuts that pointed to a server that has not been in production for over a year. Powering on that server found none of the latest files and there was nothing at the old IP of that server that was housing them currently. Then it hits me on the way to church – Offline Files on the workstation. It turns out that during the era of the previous domain controller the Folder Redirection was not done properly and when there was a migration to a new File Server these few clients had kept a pointer to the old file server with Offline Files. All file changes and new files were stored in the local Offline Files cache up to the size limit of that cache. I had to do the following to gain access to the cache to copy all data to the newer file server:
Recovering Offline Files Cache Due to Bad Folder Redirection Link
Go through a long process of changing folder ownership one sub-folder at a time to drill down to the user’s data in a path similar to the one below. There will be several subdirectories to look through before finding the files needed. Please refer to this Microsoft TechNet Article for details on how.
Once access is gained into the folder, copied the contents to an alternate location.
Opened a Command Prompt and drilled down into that new folder.
Typed in the following command:
*.* /T /G email@example.com:F
then confirming the change to apply Full Permissions to all files and folders that were copied there.
Copied the newly changed files into the appropriate place on the new file server and verified with user that their files were there as expected.
This won’t save everything but is the last option for this particular peculiar issue on the clients server.
If your company is using Folder Redirection or Offline files, then contact us for assistance.
There is often the case that a female user will have a name change due to change in marital status. Here is the basics of how to change their name in both Active Directory and Office 365.
Active Directory User Changes Name objects
Open Active Directory Users and Computers
Find the user needing the changed name, right click on them and choose the “Rename” option.
Change the user’s name as needed then press Enter then in the window that opens make all the further changes needed and click the “OK” button.
Click on the View menu at the top and check the “Advanced Features” option.
Double click on the users new name to open their Properties. Change the email address if needed in the General tab.
Choose the “Attribute Editor” tab, scroll down the list to “proxyAddress” attribute and double click it. Click on the current SMTP:firstname.lastname@example.org and click the “Remove” button then change it to a smtp:email@example.com then click the “Add” button.
Type in SMTP:firstname.lastname@example.org for the user and then click the “Add” button. Click the “OK” button on this window and the one beneath it.
Make sure to also rename the users Redirected Folder if there is one created via Group Policy
Run a manual sync of the DirSync tool via the Microsoft Forefront Identity Manager console.
Changes to Office 365
Make sure the Windows Azure Active Directory Module for Windows PowerShell is installed properly
Open Windows Azure Active Directory Module for Windows PowerShell as administrator
Type in the following to run signed scripts for Exchange Online:
Type in the following to enter the administrative credentials for Office 365:
$creds = Get-Credential
Enter the Office 365 Administrator credentials then click “OK” button.
Type in the following to connect to Office 365 via PowerShell:
Connect-MsolService -Credential $creds
Type in the following to connect to Exchange Online via Powershell:
Had a workstation that would regularly lose connection with connected printers, so checked the Windows services. Found that the Print Spooler terminated and would repeatedly do so even when restarted. Checked the Event Logs and found that there were several instances of Event ID 7031 – Print Spooler Terminated Unexpectedly corresponding with the Services stopping.
Fix Print Spooler terminated via the registry:
Open regedit (e.g. click Start, type regedit and press Enter)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers
depending on your OS
Under this key, there will either be the keys Version-2 and Version-3 or both
The sub-keys under these contain the printer driver configuration information, so delete all the sub-keys under Version-2 and Version-3, but not these keys themselves
Restart the Print Spooler service and test printing
If your company is having issues with Print Spooler terminated events or needs help troubleshooting network printers, then contact us for assistance.
Found the amazingly easy to use Quickbooks Install Tool that fixed common installation errors after I ran into this issue with a client on two of their new workstations, same model, when trying to install Quickbooks 2014 Premier. The client had previously contacted Quickbooks for remote installation support but the technician was unable to fix it. I tried the installation from scratch using administrative credentials and got an:
Error 1904. Module “C:\Program files\Intuit\Quickbooks 2010\ICWrapper.dll” failed to register.
Which led me to the Quickbooks Support Forums that revealed a new tool in the Quickbooks support arsenal – the Quickbooks Install Tool. This handy tool does a repair of several key components for installing software, reboots the computer, and then restarts the installation before Windows finishes booting completely to avoid any conflicts. It works like a charm.
If your company is using Quickbooks for your accounting or customer database and need help getting Quickbooks Install Tool to fix your installation issues, then contact us for assistance.
This was one of the most exasperating things that I have worked on in some time. The client got a bonded ADSL PPPoE connection from CenturyLink with 40Mbps Up by 2Mbps Down. The PPPoE was to authenticate the connection to CenturyLink.
Reconfigure the Technicolor C2000T modem into Bridged Mode
Login to the modem and click on the “Wireless” button
Disable the wireless completely and click on the “Apply” button
Click on the “Advanced” button then click on the “DHCP Settings” along the left hand menu
Disable DHCP completely and click the “Apply” button
Click on the “WAN Settings” and change the ISP Protocol to “Transparent Bridging” then click on the “Apply” button
Reboot the modem and move on to configuring the Juniper router
Configure the Juniper SRX 210 for the Bonded ADSL PPPoE connection
Enter the following commands on the router CLI:
Set the underlaying interface encapsulation to be PPP-Over-Ethernet:
set interfaces ge-0/0/0 unit 0 encapsulation ppp-over-ether
Set PPP Options with Authentication method CHAP:
set interfaces pp0 unit 0 ppp-options chap default-chap-secret YOUR-PASSWORD
set interfaces pp0 unit 0 ppp-options chap local-name YOUR-USERNAME
set interfaces pp0 unit 0 ppp-options chap no-rfc2486
set interfaces pp0 unit 0 ppp-options chap passive
Set the PPPoE Options to the underlaying interface along with connection options:
set interfaces pp0 unit 0 pppoe-options underlying-interface ge-0/0/0.0
Set the the pp0 interface to automatically negotiate the IP address:
set interfaces pp0 unit 0 family inet negotiate-address
Set the security zone pp0.0 interface WAN (untrust):
set security zones security-zone WAN interfaces pp0.0
If you are experiencing any fragmentation issue, you may want to adjust the tcp-mss setting as below, this was the part that I left out and had random websites not connecting:
set security flow tcp-mss all-tcp mss 1300
If your company is using a Juniper JunOS router or CenturyLink Bonded ADSL PPPoE connection to the internet, then contact us for assistance.