Is this a remake of an old movie?

Posted: December 12, 2015 in SBS 2011

Source: Is this a remake of an old movie?


OneDrive for Business and/or SharePoint Libraries Synced

If you had your OneDrive for Business library and/or other SharePoint libraries synced and then you upgraded from Office 2010/2013 to Office 2016, there is an excellent chance that syncing will stop.  It may be coincidence that this showed up along with an upgrade to Windows 10, but the primary issues seem to be with Office 2013.

Try This First

Open task manager and see if OneDrive for Business is running, or look in systray for the blue clooud icon indicating it is trying to sync.  If it is not running, go to the start menu (Windows 7 or 10) or look in Applications (Windows 8/8.1) and open OneDrive for Business.  You won’t see anything unless you look in systray again.

If it is running, either because you started it or it was already running, right-click on the systray icon and see if it brings up the context menu.  Hopefully it will, and you should choose repair. Let it run to see if that fixes your problem by then seeing if things start to sync.

I was not so lucky.  I got no context menu when I right-clicked.  More than that, I should 13,000+ files syncing (size of all my synced libraries) and it never changed.

What Worked for Me

I tried several things, none of which actually did any good towards fixing the sync problem, but for your information, and in hopes maybe they would work for you, here they are:\

  • Started OneDrive for Business, restarted the computer and tried again.  Nope.
  • Ran quick repair on Office (installed from Office 365 BTW).  Nope
  • Ran full repair on Office.  Nope.
  • Opened Office 365 and went to each library and tried sync icon.  Nope.

If you too got none of those to work what you should do next is uninstall Office 2016.  Don’t panic about settings like Outlook profiles, signatures, etc.  They won’t disappear on you.

For the next step, rename the synced folders on my local drive.  In my case, the local copies were all on Drive C:, so navigated toC:\Users\<myprofile>.  If you synced ShareSharePoint  libraries you will see a folder Named SharePoint.  DO NOT DELETE THESE FOLDERS OR FILES!!  Rename it to have an extension of .old (you can do anything you want to get rid of the original name, but I would just add some sort of extension and will explain why later).  Doing this AFTER removing Office 2016 doesn’t give you an error that the files are in use.

Now rename the OneDrive for Business folder.  It, too, in in your user profile, with a file name of One Drive – <domain> where domain is your Office 365 user domain.  Add .old to it as well, for example.

Now re-install Office 2016.  If your source is Office 365, open the portal, click on the gear wheel, and choose Office 365 Settings, then either Software (if your site has not been recently upgraded) or Installs (if it has).  Click to download and install Office 2016.  If you didn’t change your computer name, then it already knows you are authenticated on that computer.

When the install is finished, start OneDrive for Business.  You may get error messages that it can’t find the libraries to sync.  If you do, then right click on the systray icon and choose Stop Syncing a Folder, then select the folder(s) and stop synching all of them.

Now, start with the SharePoint libraries you want to sync.  Open the Office 365 portal, navigate to the sites, then to each library and choose sync.  When all have finished, you can now turn your attention to OneDrive.

Here is what I had to do to avoid getting an error on sync that the file could not be opened.

  1. Stop OneDrive for Business.  You can do this in task manager, or right-click on the icon in systray and choose Exit.
  2. Open the Office 365 portal and navigate to your OneDrive for Business.
  3. Click on the sync icon, then allow it to sync.

It took a bit for my files to come across as I had a large amount in OneDrive for Business, but it finally caught up.

But Then…

I started seeing that horrible red circle with the white X appear on the folder and file names in the local folder.  I thought that very strange since all the files were synced before and there should have been no errors.  So I looked at sync errors – right-click on the icon in systray and choose that option – and saw that file after file was asking for credentials.

This is what Microsoft support describes as a known issue.  There is an update to fix it, and if you open an Office 2016 product, click on File then select Account, you will see an update button.  Click to apply the update, then reboot your computer.

While you are there, however, make sure that your Office 2016 is connected to

  • Office 365 SharePoint
  • Office 365 OneDrive for Business
  • OneDrive if you have a personal account that you also use.

I also had to do a bit of tweaking to finally get sync going again for OneDrive for Business.  I stopped the sync, did a repair, then started it again.  It did not seem to get things moving.  So I removed OneDrive for Business from the sync sites, went back to Office 365 and synced it again.  Finally, when it started reporting “need credentials,” I went off to do something else.  When I came back several hours later everything had synced and no errors were reported.

Go figure.

Files Updated Locally but Never Synced to Office 365

You may have a  situation similar to mine in that I had opened and updated files locally as well as created new ones, but they never got synced to the cloud.  So the final step is to “sync locally” with those changes.  That is why it was important to keep the old local copies because those copies hold the updated files and folders.

To “sync” them, I used xcopy.exe from a command prompt.  Add the parameters “/e /s /i /d” to copy only newer files (/d with no additional parameters) and add any missing files and folders.  Assuming that your files are synced on Drive C:, the default location, try these steps:

  1.   Open cmd prompt window.
  2.   Navigate to C:\users\<profilename>.
  3.   Look for the folder SharePoint and the one you renamed to SharePoint.old.
  4.   Enter the command xcopy sharepoint sharepoint.old /e /s /d /i
  5.   This should copy the files that are newer to the local syced folders and then in turn up to Office 365.
  6.   Repeat the command for OneDrive for Business new folder and the old, renamed one.  Be sure and use ” around the directory name, as in xcopy “onedrive for business.old” “onedrive for business” /e /s /d /i.  Replace the directory names in this example with the actual directory names on your drive.

When everything has synced to Office 365 and you are comfortable with the files that are local and in the cloud, you can safely delete the old, renamed folders from your drive.


Strange Behavior

I first noticed this for a client who had to reboot their server during the middle of the day.  Suddenly, a server that was running just fine, was no longer “visible” to client machines.  They could not connect to shares, could not ping the server, and were seemingly disconnected.  What was even stranger was that the server had no difficulties “seeing” those client machines.  Moreover, I was unable to remote desktop into the server from anywhere.

When I finally got on the computer, I looked at Network and Sharing Center and was shocked to see that the network connection showed Public and the network identification was for an unknown network.  How did that happen, and how could I make that go away?

What Didn’t Work

I tried restarting the server, restarting the router, restarting the switch, restarting the client machines all to no avail.  Then I hit on this:

The Solution

I opened Services and scrolled down to Network Location Awareness.  It was running, but it was set to start automatically.  I changed that to Automatic – Delayed Start, then restarted the service.

Voila.  The network went back to Domain with proper identification and suddenly everybody and everything on the network was connected again.

Seems as though the service did not have enough time to detect the network and set it properly.  I wish I had a great answer for why this starting happening, but I don’t as of yet.  Just happy that the fix was easy and hope it helps you at some point.  Actually I hope it doesn’t which means you don’t have the problem.

I have seen this on one and only one server. It was a 2012 R2, but I have subsequently seen the issue reported (but not solved) for 2008 R2 as well.


In my previous post, I listed the registry change to get sent email into the shared mailbox sent folder; otherwise it ends up in the sent folder of the primary email account.  Turns out the very same thing happens to deleted items, but there is also a registry key that will fix that.

  1. Close Outlook if it is running.
  2. From the search bar in Windows 10, type regedit and then click on the result to run.  In Windows 7 click Run and type regedit then click OK. Or from Windows 8 search, type regedit and run it.
  3. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\General.Note Office 2013 uses 15.0, Office 2010 uses 14.0, 2007 12.0 instead of 15.0
  4. In the right hand pane, right-click and choose New DWORD.
  5. Type DelegateWastebasketStyle for the name and press enter.
  6. Right-click on the newly created entry and choose Modify.
  7. Enter 4 for the value.
  8. Exit regedit.
  9. Restart Outlook.

You are done.


What Are Shared Mailboxes

Although shared mailboxes are a feature of Exchange Server, I will focus more their use in Office 365.  A shared mailbox there is one which doesn’t require a specific user license but is created with access granted to other users how do have Exchange licenses. Additionally, they can be granted permissions as well.

Why use shared mailboxes and not just use a distribution list?  When you use a distribution list, incoming mail is forwarded to each person on the distribution list, and in general it is mixed with all the email for all addresses associated with that person.  In other words, mail from one particular address is not distinguished and separated.

A bigger problem can occur when sending replies or new emails. Although  inbound mail is sent to everyone on the distribution list, there is no guarantee that any replies, or new emails, will be copied to those recipients as well.  Keeping all of the sent and received emails together is at best challenging.

Shared mailboxes solve this problem.  It has its own set of standard folders such as inbox, sent, etc., and you can create custom folders.  If you have send permissions you can send from its email address.

So What Is the Problem?

Standard behavior for Outlook is to put all sent mail into the primary mailbox Sent folder, no matter what email address or mailbox you send from.  If you have all of the email related to the shared mailbox in its container, why would you want to mix sent items with your own?

There is a Solution

First, close Outlook if it is running.  While you can make the change while it is running, it needs to be restarted before it will work, so you might as well do it now.

From the search bar in Windows 10, type regedit and then click on the result to run.  In Windows 7 click Run and type regedit then click OK. Or from Windows 8 search, type regedit and run it.

Expand HKEY_CURRENT_USER and keep expanding until you have reached

HKEY_CURRENT_USER|Software\Microsoft\Office\16.0\Outlook\Preferences

Note this is for Office 2016.  If you are using Office 2013, change the 16.0 to 15.0; Office 2010, change the 16.0 to 14.0.

In the right hand pane, right-click and choose New->DWORD.   For the value type

DelegateSentItemsStyle

and press Enter.  Then right-click on that key when it shows up and click Modify.  In the Value data box, enter 1 and click OK.

Exit the registry editor.

Start Outlook and give it a try.  You will see sent items for the shared folder in its sent folder, not in your primary email sent folder.

 

 

Find TechEvents on Thumbtack

Posted: August 7, 2014 in SBS 2011
Tags: ,

You can now request network and business services support from TechEvents at thumbtack.com.

Visit IT Support to find out more.

At Thumbtack, you can find a wide variety of services to choose from, not just IT.

Always feel free to visit directly at TechEvents .


Almost Gone!!!!!

By midnight, the virus outbreak will have ended, although experts are warning it may reoccur in another form in a year.  Enjoy this foolish day.

Late Breaking News!

Field reports indicate the effects of both viruses have started to disappear.  Exerts believe they will be  completely gone by midnight tonight.

New Computer Virus Detected Around Midnight

This virus represents a serious threat unlike any seen before.  Known as the 401-14 virus, it can infect a variety of devices:

All versions of Windows

  • All versions of Apple OS
  • Android
  • Linux
  • IBM Mainframes
  • And a few other OS included embedded ones

The first sign, apparently, that a device has become infected is that it runs significantly faster.  Even on a slow network connection, upload and download speeds increase by a factor of 10 or in some extreme cases over 100 times.

Once everything is running faster, which the virus has been programmed to detect, it begins its real work.  Watch for the following signs:

  • Security flaws are patched in Windows IE
  • Suspicious web sites are blocked automatically
  • Phishing and spam messages are sent automatically to your deleted folders
  • Programs that did not install properly, or would not run, are automatically re-installed to run

Some users with mixed OS devices, like those using Windows on desktops and laptops but also using Macs and iPads or Chrome books, have reported unexpected compatibility between programs and data on these devices.  This has prompted one well known security specialist, who wished to remain anonymous because of the work he does for government agencies, warned that if this virus spreads, it could do unprecedented damage to manufacturers and users alike.

As more information comes in from the field today, I will update this post.

New Human Virus Discovered 

If a massive viral outbreak for computing devices just discovered wasn’t scary enough, then consider an almost simultaneous announcement from the Center for Human Disease Control of a heretofore unknown strain of virus that infects humans.  Coming on the heels of the computer virus announcement, the Center has tentatively named this new virus the H-401-14 virus.

Doctors and scientists have so far only isolated a few but scattered outbreaks.  Hospitals and clinics have been altered to be on the lookout for the following symptoms:

  • Patients who suffered from severe depression and anxiety to milder forms of just being grumpy or unpleasant undergo a sudden personality change and are kind to strangers, jovial with those around them, and in some cases, break into song.
  • A more serious effect is that the virus can irreversibly destroy any signs of HIV, HEP-A/B/C, and antibacterial drug resistant pneumonia and tuberculous.
  • In one reported outbreak in the nation’s capital city, GOP and Democratic members of Congress were seen having dinner together (burgers on gluten-free bus with kale and chocolate organic shakes) and then retiring to work on legislation for immigration, tax reform, and income inequality.
  • In several states, outbreaks reportedly are linked to roll backs on re-redistricting.

Be careful about rumors that might prove to be so outrageous as to be unfounded.  For example, a possible mutation of this virus has been shown to limit contributions from wealthy corporations and individuals that have flourished since the Supreme Court ruling in Citizens United, but despite being a person, corporations are as yet unaffected by this virus.

We can only hope and pray that the worst effects, even if it becomes a pandemic, is that everyone will break into song.  But it will be a brave, new world.

In the meantime, enjoy your day and check back for updates.