Reset Offline Files Cache in Windows 7

Easiest way to do this:

1. Navigate to the following location in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc\Parameters 

2. Create a new DWORDValue called FormatDatabase , with the value 1
3. Reboot (the new key we created will delete itself after rebooting along with the Offline cache)

You can then set the network resource to always be available offline again, and it will begin the synchronization.

SBS 2003 CALs are missing

This happens frequently. 

Copy the following red text into a txt file, rename it to sbscal.bat and run it. You should be all set afterwards. 

net stop LicenseService
rename %windir%\system32\licstr.cpa %windir%\System32\licstr.cpa.old
copy %windir%\system32\autolicstr.cpa %windir%\system32\licstr.cpa
net start LicenseService

Malwarebytes’ Anti-Malware Seems to be Lagging Behind

For years, I’ve sworn by MBAM, and it’s always come through for me. I’d always done a MBAM full scan followed by a virus scan with whatever they had installed, and then a ComboFix scan.

Lately however, MBAM has been coming up clean, and ComboFix has been doing the bulk of the work. 

Office365 – Set All User Account Passwords to NOT Expire

Go here: http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh124998.aspx 

Download and install these two things according to the OS architecture of the machine you’re currently using to perform this operation:
Microsoft Online Services Sign-In Assistant (IDCRL7) – (32 bit version)
Microsoft Online Services Sign-In Assistant (IDCRL7) – (64 bit version)

AND

Microsoft Online Services Module for Windows PowerShell – (32-bit version)
Microsoft Online Services Module for Windows PowerShell – (64-bit version)

NOTE: Norton 360 classified the Microsoft Online Services Module download as a threat for me, and removed it from my downloads. Be prepared to disable your A/V.

Once these are installed, Click the start button, in the search field type Microsoft Powershell, open the result “Microsoft Online Services Module for Windows PowerShell”

Enter the following command:

Connect-MsolService

You will be prompted for credentials. Use the account administrator credentials.

Type the following, and hit enter.

Set-ExecutionPolicy Unrestricted

press Y for yes, and hit enter

Copy and paste the entire next command

$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection
Import-PSSession $Session

You will be Prompted for credentials again. Enter them, and hit ok. You’ll then see warninds about “You connection has been redirected to the folling URI”. This is ok. NOTE: The last line of that command is still waiting to be run. You need to hit enter for it to execute. Once it’s done, use the following command to set all user account passwords to never expire:

Get-MSOLUser | Set-MsolUser -PasswordNeverExpires $true

Use Windows PowerShell to manage Office 365 – Office 365 for enterprises

Use Windows PowerShell to manage Office 365

Topic Last Modified: 2012-03-22

As an administrator, you can use Windows PowerShell cmdlets to accomplish many Microsoft Office 365 administrative tasks such as user management and domain management. This topic includes information about Windows PowerShell and how to install the cmdlets for Office 365.

You can also manage Microsoft Exchange Online with Windows PowerShell cmdlets. For more information, see Use Windows PowerShell in Exchange Online.

What do you want to do?

Learn about Windows PowerShell

Install the Office 365 cmdlets

Connect Windows PowerShell to the service

About Windows PowerShell

Windows PowerShell is a task-based command-line shell and scripting language designed for system administration. Unlike most shells, which accept and return text, Windows PowerShell is built on top of the Microsoft .NET Framework common language runtime (CLR) and the .NET Framework, and accepts and returns .NET Framework objects. Windows PowerShell introduces the concept of a cmdlet (pronounced “command-let”), a simple, single-function command-line tool built into the shell. Cmdlets have the following naming convention: a verb and noun separated by a dash (-), such as Get-Help, Get-Process, and Start-Service. Windows PowerShell includes more than one hundred basic core cmdlets. For more information about Windows PowerShell, see the Windows PowerShell Getting Started Guide.

There are many Office 365 cmdlets you can use to perform a variety of administrative tasks. For more information about the various tasks you can perform using cmdlets, see Windows PowerShell cmdlets for Office 365.

Install the Office 365 cmdlets

To begin using the Office 365 cmdlets, you first need to install them. The requirements for installing the Office 365 cmdlets are as follows:

You can install the cmdlets on a Windows 7 or Windows Server 2008 R2 computer.

You must have Windows PowerShell and the .NET Framework 3.5.1 enabled.

You must install the Microsoft Online Services Sign-in Assistant. Download and install one of the following from the Microsoft Download Center:

Microsoft Online Services Sign-In Assistant (IDCRL7) – 32 bit version

Microsoft Online Services Sign-In Assistant (IDCRL7) – 64 bit version

To install the cmdlets, perform the following steps:

Download one of the following from the Microsoft Download Center:

Microsoft Online Services Module for Windows PowerShell (32-bit version)

Microsoft Online Services Module for Windows PowerShell (64-bit version)

To install the cmdlets, double-click the AdministrationConfig.msi file.

The installer adds the program to your Start menu and a shortcut to your desktop.

Connect Windows PowerShell to the service

Click the Microsoft Online Services Module shortcut to open a Windows PowerShell workspace that has the cmdlets. Alternatively, you can load the Office 365 cmdlets manually by typing import-module MSOnline at the Windows PowerShell command prompt.

For more information about cmdlets, you can do the following:

Get a list of cmdlets by typing the following at the command prompt: get-module MSOnline

View the Help file for a cmdlet by typing the following at the command prompt: get-help -detailed

See Also

Windows PowerShell cmdlets for Office 365

via Use Windows PowerShell to manage Office 365 – Office 365 for enterprises.

How to configure user passwords to never expire in Office 365

You need to download the Microsoft Online Services Sign-in Assistant

2)       And also you need to install the PowerShell Msonline Module.

System requirements

Supported Operating Systems: Windows Vista, Windows Vista 64-bit Editions Service Pack 1, Windows Vista Business, Windows Vista Business 64-bit edition, Windows Vista Enterprise, Windows Vista Enterprise 64-bit edition, Windows Vista Home Basic, Windows Vista Home Basic 64-bit edition, Windows Vista Home Premium, Windows Vista Home Premium 64-bit edition, Windows Vista Service Pack 1, Windows Vista Ultimate, Windows Vista Ultimate 64-bit edition, Windows XP, Windows XP Professional Edition, Windows XP Service Pack 2, Windows XP Service Pack 3, Windows XP Tablet PC Edition

Requirements provided to subscribers via the Microsoft Online Services Administration Center or My Company Portal. This product intended for use with Microsoft Online Services only.

Microsoft Online Services Sign-in Assistant Setup (now required for MSONLINE powershell)

http://office.microsoft.com/en-us/word-help/redir/XT102098586.aspx?CTT=5&origin=HA102065466

 

PowerShell Msonline Module

http://g.microsoftonline.com/0BD00en-US/85

 

After the download is completed, please copy and paste this section into the PowerShell window. And enter your credentials.

 

1)       $Cred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $Cred -Authentication Basic –AllowRedirection

Import-PSSession $Session

 

2)       Import-Module MSOnline

$Creds = Get-Credential

Connect-MsolService –Credential $Creds

3)       Set-MsolUser -UserPrincipalName contoso@microsoft.com -PasswordNeverExpires $true

Note If you want to change the setting for all the users in an organization, run the following command:

Get-MSOLUser | Set-MsolUser -PasswordNeverExpires $true

 

N.B Replace the red highlight text with your e-mail address.

 

Sam Dawsen | E-mail: v-sadaws@microsoft.com

via Microsoft Office 365 Community.

Microsoft Office 365 Community

You need to download the Microsoft Online Services Sign-in Assistant

2)       And also you need to install the PowerShell Msonline Module.

System requirements

Supported Operating Systems: Windows Vista, Windows Vista 64-bit Editions Service Pack 1, Windows Vista Business, Windows Vista Business 64-bit edition, Windows Vista Enterprise, Windows Vista Enterprise 64-bit edition, Windows Vista Home Basic, Windows Vista Home Basic 64-bit edition, Windows Vista Home Premium, Windows Vista Home Premium 64-bit edition, Windows Vista Service Pack 1, Windows Vista Ultimate, Windows Vista Ultimate 64-bit edition, Windows XP, Windows XP Professional Edition, Windows XP Service Pack 2, Windows XP Service Pack 3, Windows XP Tablet PC Edition

Requirements provided to subscribers via the Microsoft Online Services Administration Center or My Company Portal. This product intended for use with Microsoft Online Services only.

Microsoft Online Services Sign-in Assistant Setup (now required for MSONLINE powershell)

http://office.microsoft.com/en-us/word-help/redir/XT102098586.aspx?CTT=5&origin=HA102065466

 

PowerShell Msonline Module

http://g.microsoftonline.com/0BD00en-US/85

 

After the download is completed, please copy and paste this section into the PowerShell window. And enter your credentials.

 

1)       $Cred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $Cred -Authentication Basic –AllowRedirection

Import-PSSession $Session

 

2)       Import-Module MSOnline

$Creds = Get-Credential

Connect-MsolService –Credential $Creds

3)       Set-MsolUser -UserPrincipalName contoso@microsoft.com -PasswordNeverExpires $true

Note If you want to change the setting for all the users in an organization, run the following command:

Get-MSOLUser | Set-MsolUser -PasswordNeverExpires $true

 

N.B Replace the red highlight text with your e-mail address.

 

Sam Dawsen | E-mail: v-sadaws@microsoft.com

via Microsoft Office 365 Community.

How to Reset My Toolbox in Gimp | eHow.com

Instructions

1

Open the GIMP image editor. It’s not necessary to open an image when resetting the toolbox.

2

Inspect the bottom edge of the toolbox. Notice a yellow circular arrow; this is the toolbox reset button.

3

Click on the toolbox reset button while simultaneously pushing the “Shift” key.

4

Click on “Reset” when you see a prompt asking if you want to reset the toolbox values.

Tips & Warnings

Also reset the toolbox by clicking on “Edit>Preferences>Reset.” However, this resets all of the GIMP settings, rather than just the toolbox.

via How to Reset My Toolbox in Gimp | eHow.com.

How to Reset Photoshop to default settings

How to Reset Photoshop to default settings

Photoshop resetting settings When working from Windows, I use Photoshop to do much of my graphical work. Gimp is also a great equivalent for those who prefer working from Linux (can be used in Windows as well). A typical problem people encounter when playing around with Photoshop is that of changing the default settings during experimentation and then forgetting what the baseline setting were. If you have been messing with Photoshop for long enough, you know exactly what I mean.

Well, the good news is that there is a simple fix that allows you to reset all of your Photoshop CS2 or Photoshop CS3 settings and preferences back to factory default.

How to reset Photoshop preferences (In Windows):

First, hold down all three Ctrl+Alt+Shift buttons

Now “while keeping those button held,” simply open Photoshop or a file that opens with Photoshop

As Photoshop loads, you should get a prompt asking if you would like to “delete the Photoshop settings file”, Click yes

You should now have a fresh slate with all of the settings returned to their default.

Note: I have found that this process is kind of finicky and doesn’t always work. I have had the best results pressing Ctrl+Alt+Shift and clicking the photoshop shortcut from the start menu in Windows.

Another method that works well if you have another shortcut or image that can be opened with Photoshop is to do the following:

Press and hold Ctrl+Alt+Shift then (right mouse click) a Photoshop shortcut or Image file and select Open.

Similar Simple Solutions

Photoshop – Unable to continue because of a hardware or system error

Installing additional photoshop fonts

How to Reset Droid X to Factory Settings

Photoshop CS4 Open Files in New Window

Remove the Register Photoshop Prompt

via How to Reset Photoshop to default settings.

Logon Type Codes Revealed

Logon Type Codes Revealed.

Event IDs 528 and 540 signify a successful logon, event ID 538 a logoff and all the other events in this category identify different reasons for a logon failure. However, just knowing about a successful or failed logon attempt doesn’t fill in the whole picture. Because of all the services Windows offers, there are many different ways you can logon to a computer such as interactively at the computer’s local keyboard and screen, over the network through a drive mapping or through terminal services (aka remote desktop) or through IIS. Thankfully, logon/logoff events specify the Logon Type code which reveals the type of logon that prompted the event.

Logon Type 2 – Interactive

This is what occurs to you first when you think of logons, that is, a logon at the console of a computer. You’ll see type 2 logons when a user attempts to log on at the local keyboard and screen whether with a domain account or a local account from the computer’s local SAM. To tell the difference between an attempt to logon with a local or domain account look for the domain or computer name preceding the user name in the event’s description. Don’t forget that logon’s through an KVM over IP component or a server’s proprietary “lights-out” remote KVM feature are still interactive logons from the standpoint of Windows and will be logged as such.

Logon Type 3 – Network

Windows logs logon type 3 in most cases when you access a computer from elsewhere on the network. One of the most common sources of logon events with logon type 3 is connections to shared folders or printers. But other over-the-network logons are classed as logon type 3 as well such as most logons to IIS. (The exception is basic authentication which is explained in Logon Type 8 below.)

Logon Type 4 – Batch

When Windows executes a scheduled task, the Scheduled Task service first creates a new logon session for the task so that it can run under the authority of the user account specified when the task was created. When this logon attempt occurs, Windows logs it as logon type 4. Other job scheduling systems, depending on their design, may also generate logon events with logon type 4 when starting jobs. Logon type 4 events are usually just innocent scheduled tasks startups but a malicious user could try to subvert security by trying to guess the password of an account through scheduled tasks. Such attempts would generate a logon failure event where logon type is 4. But logon failures associated with scheduled tasks can also result from an administrator entering the wrong password for the account at the time of task creation or from the password of an account being changed without modifying the scheduled task to use the new password.

Logon Type 5 – Service

Similar to Scheduled Tasks, each service is configured to run as a specified user account. When a service starts, Windows first creates a logon session for the specified user account which results in a Logon/Logoff event with logon type 5. Failed logon events with logon type 5 usually indicate the password of an account has been changed without updating the service but there’s always the possibility of malicious users at work too. However this is less likely because creating a new service or editing an existing service by default requires membership in Administrators or Server Operators and such a user, if malicious, will likely already have enough authority to perpetrate his desired goal.

Logon Type 7 – Unlock

Hopefully the workstations on your network automatically start a password protected screen saver when a user leaves their computer so that unattended workstations are protected from malicious use. When a user returns to their workstation and unlocks the console, Windows treats this as a logon and logs the appropriate Logon/Logoff event but in this case the logon type will be 7 – identifying the event as a workstation unlock attempt. Failed logons with logon type 7 indicate either a user entering the wrong password or a malicious user trying to unlock the computer by guessing the password.

Logon Type 8 – NetworkCleartext

This logon type indicates a network logon like logon type 3 but where the password was sent over the network in the clear text. Windows server doesn’t allow connection to shared file or printers with clear text authentication. The only situation I’m aware of are logons from within an ASP script using the ADVAPI or when a user logs on to IIS using IIS’s basic authentication mode. In both cases the logon process in the event’s description will list advapi. Basic authentication is only dangerous if it isn’t wrapped inside an SSL session (i.e. https). As far as logons generated by an ASP, script remember that embedding passwords in source code is a bad practice for maintenance purposes as well as the risk that someone malicious will view the source code and thereby gain the password.

Logon Type 9 – NewCredentials

If you use the RunAs command to start a program under a different user account and specify the /netonly switch, Windows records a logon/logoff event with logon type 9. When you start a program with RunAs using /netonly, the program executes on your local computer as the user you are currently logged on as but for any connections to other computers on the network, Windows connects you to those computers using the account specified on the RunAs command. Without /netonly Windows runs the program on the local computer and on the network as the specified user and records the logon event with logon type 2.

Logon Type 10 – RemoteInteractive

When you access a computer through Terminal Services, Remote Desktop or Remote Assistance windows logs the logon attempt with logon type 10 which makes it easy to distinguish true console logons from a remote desktop session. Note however that prior to XP, Windows 2000 doesn’t use logon type 10 and terminal services logons are reported as logon type 2.

Logon Type 11 – CachedInteractive

Windows supports a feature called Cached Logons which facilitate mobile users. When you are not connected to the your organization’s network and attempt to logon to your laptop with a domain account there’s no domain controller available to the laptop with which to verify your identity. To solve this problem, Windows caches a hash of the credentials of the last 10 interactive domain logons. Later when no domain controller is available, Windows uses these hashes to verify your identity when you attempt to logon with a domain account.