Here are the steps:
- Download Microsoft Media Creation Tool.
- Start the tool and select the option to create ISO files to install on another computer.
- Once all is downloaded and the Tool allows you to press finish – DON’T
- Check C:\ESD folder for files (as it should contain installx86.esd and installx64.esd)
- Copy ESD folder to C:\TEMP
- Convert the esd files to wim using the following command: dism /export-image /sourceimagefile:C:\$Windows.~WS\Sources\installx64.esd /SourceIndex:4
/destinationimagefile:C:\install.wim /destinationname:"Windows 10 Pro x64" /compress:max /checkintegrity
- Import the new WIM files to MDT 2013 Update 2
I did not discover this fix. I found this from TechNet forums but have since lost the link.
The fix below helped me resolve this problem.
The Active Directory integrated DNS zone _msdcs.domain.com was not found.
- Create a zone called "_msdcs.domain.com"
- Make it AD integrated
- Allow secure only updates and Click Finish
- Go back into the zone properties
- Change the replication scope to "All DCs in the Forest"
- Delete the _msdcs folder under domain.com
- Run an ipconfig /registerdns
- stop netlogon
- start netlogon
- The SRVs should populate shortly, if they already haven’t
Credit goes to users on TechNet Forums.
Here are some of the commands.
To view the Scheduler configuration:
This shows you the current sync configuration information like interval, sync policy type, next sync cycle start time etc.
To change the scheduler configuration:
This allows you to change some the following sync parameters.
To Start the Scheduler manually:
There are two synchronization options – Delta and Full.
Delta – Use this when there is an urgent change that needs to be synchronized immediately.
Start-ADSyncSyncCycle -PolicyType Delta
Full – Use this when the following changes have been made.
- Synchronization rules have been changed
- Filtering changes, which included different number of objects
- More attributes or objects are to be imported from source directory
Start-ADSyncSyncCycle -PolicyType Initial
- Check the status of the connector:
If its busy and running the sync the connector name will be returned.
More info – Azure Documentation
In this I received the Printer Spooler Error on Windows 8.1:
"windows cannot connect to the printer. the local print spooler service is not running. please restart the spooler or restart the machine."
This can be fixed in 2 ways.
- Go to Control Panel > Administrative Tools and open Services. Find the printer spooler service and check the status of it. If its Started, then Restart the service.
- Right Click on Windows button and select Command Prompt (Admin). Type in the following command: net stop spooler && net start spooler
- TIP! – This will also work on Windows 7/10
This is a script to shutdown and restart an application (i.e. jboss) on windows.
It also renames the application generated log file(s).
taskkill /f /t /fi “WINDOWTITLE eq 3 Scheduler”
for /F “tokens=1,2” %%d in (‘date /T’) do set day=%%d & set date=%%e
ren “D:\logs\scheduler\scheduler.log” %dateserial%-scheduler.log
start /min “3 Scheduler” cmd /c “D:\scheduler\bin\run.bat”
Note: I found the base script from here
If you find logging in to Windows Live Mail using your browser boring and annoying, then it is now possible to configure your desktop email clients using the following settings.
Windows Live Mail POP3 Server: pop3.live.com
POP3 SSL required: Yes
User name: Your Windows Live ID, for example firstname.lastname@example.org
Password: The one you use to sign in to Windows Live
Windows Live Mail SMTP server: smtp.live.com
Authentication required: Yes
TLS/SSL required: Yes
We all know that Exchange Server 2007 is 64-bit only. Is it possible to manage it from 32-bit Windows Vista machine? The answer to this question is yes. There is a 32-bit version of Exchange Management Tools. It includes:
* Exchange Management Console (EMC)
* Exchange Management Shell (EMS)
* Exchange Best Practice Analyzer (ExBPA)
* Exchange Troubleshooting Assistant (ExTRA)
* Help files
Remember these tools require MMC 3.0, the .NET Framework 2.0 and Windows PowerShell. If you don’t have them, you will be prompted to install them. You can run these tools on Windows XP Pro 32-bit edition or Windows Vista 32-bit edition.