Showing posts with label OSD. Show all posts
Showing posts with label OSD. Show all posts

Wednesday, June 26, 2013

IAAS ,SAAS, and PAAS --> Windows Azure.

Infrastructure as a Service (IAAS)

Vendors provide the infrastructure to build solutions, and you rent the hardware such as servers, load balancers, a firewall, and cables. You then configure these remotely and install your solutions on them. You can scale up by requesting more servers and reconfiguring the load balancer without purchasing more hardware. You can scale down at any time by reconfiguring the infrastructure you rented from the cloud service provider. This vendor approach is called Infrastructure as a Service (IaaS) because a customer can rent the infrastructure without having to forecast and provision for the highest possible demand in advance. In this approach, you are responsible for correctly configuring the rented infrastructure.

Software as a Service (SAAS)

In another approach, you can rent a service offered by the vendor and then configure the service by using the interface provided by the vendor, without having to know what infrastructure the vendor uses to provide that service. This approach is called Software as a Service (SaaS) because you pay to use defined services. For example, Microsoft Exchange Online carries a per-mailbox charge. To configure it, you use a web application supplied by the vendor to request mailboxes, and name and dimension them. You receive a password for that user and nothing else is necessary—users can access their mailboxes immediately.

Platform as a Service (PASS)

The third approach is Platform as a Service, or PaaS. In this approach, you rent a platform on which you deploy your applications without configuring the infrastructure and without the limitations of the SaaS approach.
The Windows Azure platform fits best in the PaaS category, because it doesn’t provide access to the underlying virtualization environment or operating system details such as the network interface, IP configuration, and disk management.

Copied.

Thursday, May 30, 2013

OSD- SMSTS.LOG file locations -SCCM

Hey friends,

If we are going to deploy Operating System SMSTS.LOG is very important to review. With smsts.log we can easily understand about our successful or unsuccessful deployment.

The SMSTS.LOG can be stored in one of 7 locations, depending on the stage of the build and the architecture of the OS:

WindowsPE, before HDD format:               x:\windows\temp\smstslog\smsts.log

WindowsPE, after HDD format:                       x:\smstslog\smsts.log

Windows, SCCM agent not installed:         c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

Windows, SCCM agent installed:                     c:\windows\system32\ccm\logs\Smstslog\smsts.log

Windows x64, SCCM agent installed:         c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

Task Sequence completed:                               c:\windows\system32\ccm\logs\smsts.log

Task Sequence completed x64:                    c:\windows\sysWOW64\ccm\logs\smsts.log

 -------------------------------------------------------------------------------------------------------------

 Copy Method -->SMSTS.LOG file to Config Manager Server

Common Errror -->
Task Sequence: Windows 7 Image has failed with the error code (0×80070002). For more information, contact your system administrator or helpdesk operator. The computer will automatically restart in 15 minutes.

When the Task Sequence: error code (0×80070002) pops up on the screen we need to press the F8 key on our keyboard to pull up command line. 

Run the following set of commands in the command prompt to copy the smsts.log to our SCCM Server.
  • Map a drive from your SCCM server:
net use M: \\SCCMSERVERNAME\C$
  • Run the below syntax to copy the log file to the root of your SCCM server:
copy smstslog.log M:


Enjoy Troubleshooting..

:-) P





Tuesday, September 11, 2012

New Microsoft Exams .... :)

MCTS: System Center 2012

70-243 Administering and Deploying System Center 2012 Configuration Manager
As mentioned earlier this is just for ConfigMgr 2012. The other System Center 2012 products are bundled in the Microsoft Private Cloud exams.

MCSE: Microsoft Private Cloud

70-246 Monitoring and Operating a Private Cloud with System Center 2012
70-247 Configuring and Deploying a Private Cloud with System Center 2012 
All System Center 2012 products (except ConfigMgr 2012) are bundled in these exams. More information about both exams HERE
More information: Microsoft Learning

MCSA: Windows Server 2012

70-410 Installing and Configuring Windows Server 2012
70-411 Administering Windows Server 2012
70-412 Configuring Advanced Windows Server 2012 Services 
The MCSA: Windows Server 2012 certification shows that you have the primary set of Windows Server skills that are relevant across multiple solution areas in a business environment.
More information: Microsoft Learning

MCSE: Server Infrastructure

70-413 Designing and Implementing a Server Infrastructure
70-414 Implementing an Advanced Server Infrastructure
The MCSE: Server Infrastructure certification validates your ability to build comprehensive server infrastructure solutions.
More information: Microsoft Learning

MCSE: Desktop Infrastructure

70-415 Implementing a Desktop Infrastucture
70-416 Implementing Desktop Application Environments
The MCSE: Desktop Infrastructure certification validates your skills in desktop virtualization, remote desktop services and application virtualization.
70-417 Upgrading Your Skills to MCSA Windows Server 2012
If you have an MCSA: Windows Server 2008 certification, you may take Exam 417 to upgrade to the MCSA: Windows Server 2012.
More information: Microsoft Learning

MCSA: Windows 8

70-687 Configuring Windows 8
At the moment this is the only Windows 8 exam available.
70-689 Upgrading Your Skills to MCSA Windows 8 (not yet released)
The MCSA: Windows 7 certification allows you to upgrade to the MCSA: Windows 8 certification, by taking a single upgrade exam (689 – not yet released).