I recently had quite a hard time setting up a Windows share using Samba on a Mythbuntu box so here are some links and reminders. I tried several GUI apps but none worked with consistant results.
On Andy Stanley’s recent podcast “Open-Handed Staffing” (1/8/2015) he discusses a high level team member that is looking at exploring a new opportunity outside of their organization. Andy advises leaders to be open to discussing these thoughts and to not set the example of encouraging an environment that encourages secrecy. He goes on to break down the reasons for transitioning from an organization into three categories (podcast time 12:10):
- You are restless, looking for a bigger/different challenge or responsibility, bored or in need of general change.
- You encounter a better opportunity that is simply not available to be provided in your current environment.
- You just know. Sometimes a new opportunity doesn’t seem to make any sense (fiscally, geographically, community, etc.) but you can’t get it out of your head or your heart and you just know that it is what you are supposed to do.
Making large transitional changes can be stressful and draining. If you are in the middle of a transition or thinking about a new opportunity that is available, ask yourself the clarifying question “If they were to call you today and tell you that they found somebody else, would you be relieved or disappointed?”
Properly setting up a SharePoint blog can be confusing, especially the permissions. Below is a repost from the Graham Alltoft SP blog.
Permissions on SharePoint 2010 blog posts
When setting up a SharePoint 2010 blog posts on an intranet site, it can be easy to get frustrated around the setting up of permissions. You may want some users to be able to create and edit blog posts, whilst everyone else can contribute their comments to a blog post but not create their own. Pretty typical setup.
You can set your bloggers to have Contribute permissions at the root of the blog site which will allow them to create and edit blog posts. Nice and easy. However, the next out of the box permission set is ‘read only’. Giving your remaining users this permission will allow them to read blog posts only, and not allow them to add comments. There is nothing in-between at this stage.
To ensure your read only users can comment on blogs only, you need to navigate to the list where the blogs are stored, at http://YourSite.com/YourBlog/Lists/Comments/AllComments.aspx. So…
- Navigate to the all comments list (sample link above)
- On the ribbon click the ‘list’ tab
- On the ribbon click the ‘list permissions’ button
- Click the ‘stop inheriting permissions’ button on the ribbon
- Click the ‘Grant permissions’ button on the ribbon
- Whatever group or individual you want to grant permission to add their comments to blog posts, give them ‘contributor’ rights
It is also best to ensure a single user can only edit his / her own comments. To do this…
- Navigate to the all comments list (link above)
- Click the ‘list’ tab on the ribbon menu
- Click the ‘list settings’ button on the ribbon
- Click ‘Advanced settings’ under the General Settings heading
- Change the ‘item-level permissions’ section, selecting the ‘Create items and edit items that were created by the user’ option
- Click ok and test
The result of this should be that only permitted users can create blog posts, everyone else can only comment on them, and only edit their own posts. There is a plethora of other options, so have a play about to customise it to your own needs.
I recently had an issue in an environment where Office 365 was being synced with AD and a user that was renamed in AD was not getting fully synced over to the cloud. Office 365 was picking up the new name and updated email address but not the “User Name”.
You are not able to modify this field using the GUI interface, but fortunately you can manually set this field using the PowerShell command below.
Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]
More details at http://support.microsoft.com/kb/2523192
Reebok just updated their mark “logo” and I think it looks great. Check out this video which does a great job explaining the change and how they think it reflects their personality.
I recently read this great article from Smashing Magazine on “Dealing With Workaholism On Web Teams”.
Other good articles on the subject:
Here are a few takeaways…
- Workaholic companies are machines that burn people out. They don’t care about creating teams. They exploit the enthusiasm of young people and dry them up. One indicator of a workaholic company is that its contractors rarely stay with it for more than a few years.
- Workaholics can be identified as the people who urge everyone else to work more, who can’t have a good laugh during working hours or who constantly talk about “the good of the company.” Continue reading
This is a fantastic quote and podcast.
“If we get better our customers will demand we get bigger.”
S. Truett Cathy (Founder, Chairman and Chief Executive Office)
From the Andy Stanley Leadership Podcast – Better Before Bigger
I was getting force closes every time I tried to open Citrix with the error of “citrix hdx engine has stopped working”. I tried several different clients and versions (both Online Plugin and Reciever).
I read that several users found the problem to be a bad print driver (see http://goo.gl/zmVIT).
My fix ended up being a printer driver as well. In the event viewer I went to “Windows Logs > Application” and found this:
Faulting application name: WFICA32.EXE, version: 220.127.116.11, time stamp: 0x4f72ac7c Faulting module name: RIC660K.DLL, version: 0.3.0.0, time stamp: 0x418008ba
Exception code: 0xc0000005
This tells me that the cause was “RIC660K.DLL”, which turns out to be a RICOH printer driver. I uninstalled the printer from device manager and Citrix started working right away without a restart.
Hope this helps some other frustrated Citrix users!
This was on Windows 8 x86
If you get the following error when trying to run Windows updates on XP…
403 – Forbidden: Access is denied. You do not have permission to view this directory or page using the creditials that you supplied.
You can find the fix at http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/403-forbidden-access-is-denied/a16db934-fd64-43db-80c0-a9e9a034cec4 or at http://support.microsoft.com/kb/946928/en-us.
The issue is with the Windows Update Agent. Updating it manual should fix your problem. Make sure to close out of IE when installing the update.