Archive for the ‘Microsoft’ Category

xxcopy “D:\Fra den mappe med mellemrum\DATA” D:\Destinationsmappe /S /H /E /VL /C /Y

/C Continues copying even if errors occur (default)
/D Copies newer files and brand new files
/H Copies hidden and/or system files also.
/S Copies directories and subdirectories except empty ones.
/E Copies directories and subdirectories, including empty ones.
/Y Overwrites existing files without prompting
/VL Enables the Very Long Path

http://connect.microsoft.com/systemsweeper

Systemsweeper er et Recovery Tool fra Microsoft til at redde inficerede maskiner.

http://community.office365.com/en-us/w/administration/477.aspx

As part of adding your domain to Office 365 for professionals and small businesses, you update the name server records for your domain to point to Office 365-hosted name servers. Some domain name registrars, such as those in Denmark and Norway for .dk and .no domains respectively, have restrictions in place that prevent this step from being completed successfully.

IMPORTANT: The information contained in this document serves as a workaround for customers who are unable to add their domain to Office 365 Small Business due to restrictions enforced by their domain registrar. We do not recommend following these steps unless you are adding a .no or a .dk domain.

To add your .no or .dk domain to Office 365, do the following.

Sign in to Office 365 for professionals and small businesses as an administrator.
In the header, click Admin and then under Management, click Domains.
Click Add a domain.
Type the domain name that you’d like to add to your account, and then click Check domain.
Click Next.
Follow the steps in the wizard to verify with Office 365 that the domain name you have added belongs to you.

After your domain has been verified by Office 365, click Cancel to exit the wizard. Next, you’ll create the DNS records that are required for Office 365 hosted services to work with your domain.

In the header, click Admin, and then under Management, click Domains.
Click the domain name that you just added to Office 365.
On the DNS manager tab, you see the DNS records that are associated with Exchange Online, Lync Online, and SharePoint Online.

Using the information on the DNS Manager tab as a guide, login at your current DNS hosting provider (which may be your domain name registrar) and manually create the same DNS records. As you create the DNS records, keep in mind the following.

The DNS records associated with Exchange Online are the following:
MX record: Configures mail routing.
CNAME record (autodiscover): Enables Outlook users to easily configure a connection with Exchange Online.
TXT record: Used for the Sender Policy Framework (SPF), which helps prevent outbound mail from being delivered to a recipient’s junk mail folder.
The DNS records associated with Lync Online are the two SRV records.
The DNS records associated with SharePoint Online are the A record and the ‘www’ CNAME record. Both of these are required for routing network traffic to your website.

NOTE: If you want to host a public-facing website on SharePoint Online but you do not see the corresponding A and CNAME records that are required, you must enable SharePoint Online hosting for your domain. For more information, see Use a vanity domain for your SharePoint Online public website address.

After you complete these steps, your domain is configured to work with Office 365 hosted services.

If you choose to add your domain to Office 365 by using the steps described here, be aware of the following implications.

SharePoint Online: If you enable SharePoint Online to host your website, the DNS records that are required to route traffic to SharePoint Online will not be created automatically by Office 365. You must manually create those DNS records at your DNS provider. You must take this extra step because Office 365 is not hosting the DNS records for your domain.
Domain troubleshooting tool: Because you did not configure your name server records to point to Office 365 name servers, the Office 365 domains troubleshooting wizard will always report that your name server records are incorrect. You can disregard this warning since you have manually created the DNS records for each of your services.
DNS manager: Office 365 for professionals and small businesses includes DNS management tools that enable you to add custom DNS records. However, although you may have created custom records by using this tool, since you have not updated your name server records for your domain, the custom records will not work. You must create the records using your current DNS hosting provider.
Future updates:When new services are added to Office 365, we will not be able to automatically add the DNS records to enable them to work on your domain. You will need to manually add these DNS records at your DNS provide

http://community.spiceworks.com/how_to/show/1752

Sysprep is a great tool to use that comes with your Windows clients on the CD. This how-to will focus on Windows XP version of sysprep, however at the end you will find multiple resources and how-tos for ImageX and Sysprep for Windows 7.

See article at Spiceworks

Måske du har været ude for at der ikke kan skabes forbindelse til delte mapper på et Samba/Linux baseret NAS-enhed. Dette har irriteret mig til hudløshed.

Den tekniske årsag skal findes i at Microsoft har valgt at standardsikkerhedspolitikken er KUN at bruge NTLMv2-godkendelse. Prøv med nedenstående. Det har virket for mig.

Kør -> Secpol.msc -> Lokale Politikker -> Netværkssikkerhed: LAN Manager-godkendelsesniveau -> Send LM & NTLM – brug NTLMv2-session…….”

Der skulle nu være hul igennem fremover.

Access NAS Windows 7
Dette virker dog kun på Pro-versionerne af Windows 7.

Hvis du har Vista eller Windows 7 Home version, er secpol ikke tilgængelig.
Her skal der redigeres direkte i registry:

– Klik på “Start”
– Skriv: “regedit”
– Tast “Enter”
– I venstre side udvides flg.:

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control

– I venstre side, klik på mappen: LSA
– I højre side, dobbeltklik på “LmCompatibilityLevel”
– Indtast nummer 1 og tryk på enter
– Genstart computeren

Så skulle det virke!

I forb. med hvilke porte som udgør hvad og hvornår har Microsoft udgivet et glimrende artikel ID:

http://support.microsoft.com/kb/832017

* TCP 135 : MS-RPC
* TCP 1025 & 1026 : AD Login & replication
* TCP 389 : LDAP
* TCP & UDP 53 : DNS
* TCP 445 : SMB , Microsoft-ds
* TCP 139 : SMB
* UDP 137 & 138 : NetBIOS related
* UDP 88 : Kerberos v5

http://support.microsoft.com/kb/926505

Det er set nogle gange, at Windows Small Business Server 2003 pludseligt går i "krampe" og ikke vil logge ind m.v.
I den forbindelse er opstået en fejl med meddelelsen om at Windows skal aktiveres. Og det på servere som har kørt i årevis.

Der er dem som mener det opstår i forb. med SBS 2003 Transition Pack:

http://support.microsoft.com/kb/914990



MS had suggested two options. 

First, they suggested renaming two files to get them out of the way. The only way
to do this was through the safe mode command prompt:

C:WINDOWSsystem32wpa.dbl
C:WINDOWSsystem32wpa.bak

This had the effect of changing the error message to a more generic WPA problem,
but the issue remained. 

Secondly, they suggested emptying the following registry key, by setting it to '0'.
 (we could still conect to the remote registry while the machine was on):

HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWPAEventsLastWPAEventLogged

This didn't change anything.

More out of desperation than inspiration. I went back to the command prompt, removed
those files again and immedaitely rebooted from the CD and ran a repair install from
it. 

2 hours later, I logged in and got the same error message again, but this time clicking
'yes' took me to the activation page. (Thankfully the network drivers were still
working). Then all that was left was downloading and re-applying 50-odd patches before
dragging myself home a shade before midnight.